yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] COMpulse:
The camera is so much better now. Less noise in the images.
[Motorola Droid 4] bofis:
:-\ I was excited to try today's (2/10) nightly with the changes you tried....unfortunately it happened again on me. This time, the 4 hardware keys lit up and the screen sorta sat there blinking (but VERY faintly so I could hardly really see what used to be on the screen) but it would go from that SUPER DIM display to totally off, and just keep blinking back and forth while ignoring all other inputs including the power button again until I held it long enough to fully reboot...

However, show of hands, who has experienced this issue, and also use Handcent? I was just looking through settings and mine had the "notification popup over lock screen fix" option checked off, which is meant to fix some devices where the popup wouldn't appear over the lock screen properly. With that option unchecked, my notification popups still appear over the lock screen just fine and do not disable the lock screen as they did when 4.4 first came out. I'm being overly hopeful here, but I wonder if that setting was maybe causing the issue randomly and will report back.
[Motorola Droid 4] stargo:
It wasn't blinking before, but is now on this nightly?

Because then I think I have actually found the right spot in the code (I'm retrying backlight init 10 times now if it fails).

Regards,

Michael
[Motorola Droid 4] bofis:
YES! It blinks now, but before that never happened. Sometimes, I guess when it happened somewhere bright enough, I could sorta make out the outlines of something on the screen, but it still never responded again. This time it was blinking between off and SUPER DIM where you still could not make anything out, but after leaving it blinking for a few minutes I rebooted the whole phone.
[Motorola Droid 4] thelolotov:
No Handcent here, and I do have the issue.
[Motorola Droid 4] stargo:
Just found a really bad kernel-bug in all kernels. On kexec-kernels this bug could well have caused the resume issues, on stock it worked by chance...

The driver for the lis3dh-accelerometer was writing to kernel-memory which was not "owned" by it, so it was overwriting random kernel-memory every-time the accelerometer was initialized or used (for example when the clock-widget updates the position for weather-information...).

Patch for this problem: https://github.com/stargo/android_k...mmit/2fa5d64a39db42426cb513775f0017241e56e110

Let's hope that's really it, but the "work-around" previously in the kexec-kernel looks really like it could have caused that.

Regards,

Michael
[Motorola Droid 4] bofis:
Thanks for all your hard work, and finding the possible source of the issue a kernel bug. Will the updated/fixed kernel be in your next build or even merged into the official then? Also, what does this mean for the kernel stuff lucize is working on too?
[Motorola Droid 4] stargo:
It will be in my next nightly and I have also submitted this fix to cm-gerrit. Now I only need to get hold of Hashcode, so he can approve the change.

I think lucize is currently merging my fixes and the fixes from Dtrail (JBX kernel maintainer) in his tree. I have to admit that I'm currently involved in too many different projects so I still haven't had enough time to really look at lucizes' kernel.I just compiled and booted it on my phone, but didn't look into merging in his stuff, yet.

Regards,

Michael
[Motorola Droid 4] lucize:
Mine has the 3g modem unstable, I think that because some usb changes from you.

Mixing it with dtrail seems to be stable, but is not clean, is full of overclocking options, I'm not so sure about power consumpion, the razr owners are pretty happy about it.

The last mix with dtrail source won't compile with standard defconfig setting and I was a bit busy this week to make it cleaner

Regards

Regards
[Motorola Droid 4] stargo:
I think you have both workarounds for errata i719 applied at the same time. The "buggy" one from motorola and the one from the upstream kernel which I committed. I realized rather late that Motorola already tried to workaround this problem...

I've reverted the Motorola one in this commit: https://github.com/stargo/android_k...mmit/aeb0c1d1272e5fa163fa7eb77a8d2a98c03c74fb

The main problem with all USB stuff is that Motorola changed way too much and implemented the same stuff in one place which is implemented in the omapzoom-kernel in a different place.

Yeah, I think a working clean version could be submitted to cm gerrit. I'll try to find the time to debug the usb-problems on your tree.

My current plan was to look through the board-mapphone*-files and search for other "use-after-free" cases.

Regards,

Michael
[Motorola Droid 4] mifritscher:
Hi,

yust of curiosity: Why did you reverted the using of the i2c block API? Isn't it much cleaner using the API than trying to do it directly? Or are there any side-effects?

Best regards,

Michael
[Motorola Droid 4] stargo:
It was overwriting the flags-field with zero, which it shouldn't do and I also tried to get back more in sync with the Motorola kernel in respect to I2C. It seems the I2C-bus sometimes gets stuck when trying to switch on the backlight, which didn't happen on the stock kernel.

Yes, the implementation looked sane (except the lis->clients->flags=0 part), but after looking at the smbus-code, I decided to revert it completely for now.

Too many variables which could influence the backlight-behavior. But it's probably something completely unrelated which is causing it...

Regards,

Michael
[Motorola Droid 4] Khiraji:
Finally taken the plunge up from CM 10.1! 2014-2-12 nightly installed! Now time to load up Titanium and put this through its paces...
[Motorola Droid 4] Hashcode:
I apologize for this non-ROM related post:

Congrats to Stargo on being added as an official CM Motorola OMAP4 device maintainer!

(probably long over due)

Please refrain from posting "congrats" messages in this thread and maybe find one of his messages to add a "thanks" to.
[Motorola Droid 4] Hashcode:
(double post bug)
[Motorola Droid 4] rblanca:
Hahaha cheers stargo! Congratulitions and thanks 4 your hard work!

P.D.: Hi hash its been a long time no see you! Hahaha good luck!
[Motorola Droid 4] stargo:
Thanks to you for all your help :)

I'll try to fix the bugs and will keep maintaining the OMAPs :)

This also means that I will shortly stop building my unofficial images, when I have merged all useful changes back into the CM repositories. The officials will then have all my fixes.

Cheers,

Michael
[Motorola Droid 4] Khiraji:
This ROM is great! My phone is wicked fast and I have yet to find something that works less than perfectly - I was having MMS issues but changing my preferred mobile network to CDMA/EvDo resolved it and now MMS works great. The only other weirdness I've found so far is that GPS seems to lose fix every now and then. I use an app called GPS Essentials to measure/play with GPS, and my phone is able to see satellites and lock onto them just fine, but it'll randomly lose the fix and then take a few seconds to re-acquire. I haven't tested this very extensively and I don't really know what the best way of trying to pin down where the bug is (or if one exists, and it isn't just my phone being screwy) but I'll report my findings.

Otherwise, everything works very well - apps load fast, UI elements load fast, the camera is sharp and responsive, and I've yet to get a FC on anything.

The 2/14 nightly is downloading now and I'll flash it as soon as it's done and see what happens. Huge THANK YOU to Stargo and everyone involved in making this fantastic ROM! :good::good:
[Motorola Droid 4] thelolotov:
SoD continues

I know you don't want to hear this, but, I'm still having SoD issues on the 13 build. Guess I need to buy an alarm clock, because it happened overnight. Lucky for me, I happened to wake up before the alarm.
[Motorola Droid 4] stargo:
I know :(

I'm currently trying to fix a rare crash in the USB-controller which might also be related to the SoD problem.

Regards,

Michael
[Motorola Droid 4] rruleford:
I know were not supposed to ask but does this mean we'll be seeing an official build? It would be awesome! Thanks stargo and congrats on your accomplishments. To thee I applaud.
[Motorola Droid 4] lucize:
for me, after applying the new omap-ehci on my git it works very well, no modem crash and no sound crash and about 18h of standby with lot of instant messaging. Usually the sound goes bad when I use too much whatsapp.

Regards
[Motorola Droid 4] stargo:
I have a report of a modem-crash with the new omap-ehci, too :(

I'm currently thinking about reverting all USB changes.

Regards,

Michael
[Motorola Droid 4] lucize:
I'm only using modem data since 14 feb and didn't had any issues, usually it crashed multiple times a day, for now I'll not make any changes on my kernel to see if in my combination is stable

I'll try to mix 2g with 3g more often maybe I can crash it.

Regards
[Motorola Droid 4] thelolotov:
Regarding USB changes, I don't think the SoDs were caused by that, necessarily, this is an issue, that, as far as I know, has existed in the ROM since its inception. They may be related, but there was never a time it didn't happen, I don't think.
[Motorola Droid 4] stargo:
I know, I had them happen before working on the ROM, too. And never on stock. But they are so rare for me (once this year), that they are hard to debug and they could be caused by different things. One (but not the only one) of which could just be the USB-problems.

Why I think so: Because you reported that you could no longer access the phone via adb when you experienced a SOD, so it seems to me the USB controller crashed.

I'm currently concentrating on getting USB working again, as this is needed for a stable phone-operation.

Regards,

Michael
[Motorola Droid 4] lucize:
the funny thing is that sound over bluetooth works (playing something in appolo or other player), but not in the speaker or headphones. I don't know what to tell, I can make the sound crash quite a lot, and is not happening during deep sleep or screen of, usually when I chat in whatsapp, this app has the ability to drive me crazy, not to mention some of the people I speak with :))

sadly it happened again on my kernel after almost 3 days of stable, next time I'll try to see if the usb is working.

the sound is going trough usb or it uses another path ?

ENTER: MOTSND SoC init
asoc: null-codec-dai <-> MultiMedia1 LP mapping ok
asoc: cpcap codec <-> omap-mcbsp-dai.2 mapping ok
asoc: cpcap in-call <-> MODEM mapping ok
asoc: cpcap fm <-> FMDummy mapping ok
asoc: cpcap bt-call <-> MODEM mapping ok
asoc: cpcap bt <-> omap-mcbsp-dai.2 mapping ok
asoc: null-codec-dai <-> omap-mcasp-dai mapping ok
asoc: BPVoice <-> omap-mcbsp-dai.2 mapping ok
asoc: cpcap stdac <-> omap-mcbsp-dai.1 mapping ok
asoc: hdmi-audio-codec <-> hdmi-audio-dai mapping ok
ALSA device list:
#0: Motorola MAPPHONE
#1: OMAP4HDMI

is cpcap be responsable of it ?

Regards
[Motorola Droid 4] stargo:
Normal sound is not sent via USB. sound/soc/omap/motsnd.c is the driver and cpcap is involved.

...
asoc: hdmi-audio-codec <-> hdmi-audio-dai mapping ok
ALSA device list:
#0: Motorola MAPPHONE
#1: OMAP4HDMI

Yes, that's possible. cpcap is involved in audio-processing.

Another idea: what happens if you disable all SND HDMI-audio-functions in your kernel? We are missing quite a bit of the HDMI framework, maybe something is trying to interact with our non-working HDMI-driver?

I'm thinking of setting these to no:

CONFIG_SND_OMAP_SOC_HDMI=y
CONFIG_SND_OMAP_SOC_OMAP4_HDMI=y
CONFIG_SND_SOC_OMAP_HDMI_CODEC=y

EDIT: Thinking about that while driving home leads me to believe you are on the right track. cpcap is responsible for power (to the bl controller), audio and usb. So if there is a problem with cpcap, all that stuff would no longer work. Do you have any dmesg where you can see a cpcap-problem or any other hint?

EDIT2: And I'm back looking at I2C. I think I may have found the issue causing the SOD. It's connected with the ambient light/proximity sensor. I'll test that and push my change if it doesn't break anything.

Regards,

Michael
[Motorola Droid 4] Mentor.37:
I can't access at /storage/sdcard0 and /storage/sdcard1 as user, I need to be superuser and in them there is a folder named Android with temporary data of app I use in the session, as the browser and the gallery.
[Motorola Droid 4] rruleford:
I've noticed SD card issue stops when I reboot recovery and wipe dalvik/cache. Issue I recently experienced was switching to ART all gapps constantly force close. Any ideas how to fix? As I hear ART is alottttt faster.
[Motorola Droid 4] COMpulse:
Tried and failed.

Basically, everything with Google in the name is crashing when I switch to ART. Google Search, Google Play Services, Google+, com.google.process.gapps, Wallet, Gmail, Settings, Google Play, etc.

I tried rebooting and clearing cache and fixing permissions. Now my FCs are Themes Provider and com.android.phone. So, still no luck. I'm using the PA 4.4 Full GApps. If it's working for other people, something must be different in my install.

EDIT:

A little googling seems to indicate that deodexed gapps causes ART to fail. Going to try a different gapps package.
[Motorola Droid 4] rruleford:
Same exact problem I had. OK I havent seen teen the SD card problem could it be cuz iam on stock ROM slot?
[Motorola Droid 4] COMpulse:
I'm still struggling with ART. Clearing cache seems to help, but I'm still getting FCs on most google apps. Tried a few different gapps packages. I'm glad I'm not the only one with this issue.
[Motorola Droid 4] rruleford:
Also getting "no APN specified for device" can't seem to find where to change APN. Installed handcent and set to Verizon and same error messag3.
[Motorola Droid 4] rruleford:
I see 11-22 on the changes but no new build? Anywayssss the no APN error is when sending MMS. Anyone know how to fix???
[Motorola Droid 4] Gilly Monster:
All things are running smooth, of course the mentioned issues, camera and such. I want to build the build prop for both GSM/CDMA together like in 4.2.2 (CM 10.1). I want to see all of the options for mobile usage instead of just Global, 1X, EVDO and LTE. I soft bricked trying to install in the stock rom slot, but I got her back up and going again. Other than that the rom is great!!!
[Motorola Droid 4] rruleford:
Hmmmmmm I didn't experience any issues installing to stock ROM slot.
[Motorola Droid 4] highlandsun:
Installing to stock rom slot? so you guys aren't keeping an actual stock rom anywhere on your phones?

I've still got stock ICS on my phone, running JB in slot 1. Been afraid to take the plunge and wipe out ICS.
[Motorola Droid 4] rruleford:
No stock ROM. If I ever get to a pickle I sbf back to stock. The extra space is niiiice.
[Motorola Droid 4] huckky:
This is a part of my system/etc/permissions/platform.xml file. would you guys please check if anything is different in your files? maybe that sdcard stuff its a permission issue. honestly i want to use this rom as daily driver but with sdcard issue i cant keep running it for long.

Thank you.

<permission name="android.permission.BLUETOOTH_ADMIN">

<group gid="net_bt_admin"/>

</permission>

<permission name="android.permission.BLUETOOTH">

<group gid="net_bt"/>

</permission>

<permission name="android.permission.BLUETOOTH_STACK">

<group gid="net_bt_stack"/>

</permission>

<permission name="android.permission.NET_TUNNELING">

<group gid="vpn"/>

</permission>

<permission name="android.permission.INTERNET">

<group gid="inet"/>

</permission>

<permission name="android.permission.CAMERA">

<group gid="camera"/>

</permission>

<permission name="android.permission.READ_LOGS">

<group gid="log"/>

</permission>

<permission name="android.permission.READ_EXTERNAL_STORAGE">

<group gid="sdcard_r"/>

</permission>

<permission name="android.permission.WRITE_EXTERNAL_STORAGE">

<group gid="sdcard_r"/>

<group gid="sdcard_rw"/>

</permission>

<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE">

<group gid="sdcard_r"/>

<group gid="sdcard_rw"/>

<group gid="sdcard_all"/>

</permission>

<permission name="android.permission.WRITE_MEDIA_STORAGE">

<group gid="media_rw"/>

</permission>

<permission name="android.permission.ACCESS_MTP">

<group gid="mtp"/>

</permission>

<permission name="android.permission.NET_ADMIN">

<group gid="net_admin"/>

</permission>
[Motorola Droid 4] stargo:
Had a typo when running rsync, the build got uploaded to the wrong directory. I've just moved it to the correct location.

In the merged changes from dhacker are changes related to MMS, maybe this fixes your problem.
[Motorola Droid 4] stargo:
That should be fixed in the 2013-11-22-build, and on the next build it should also be possible to edit the APN settings (for gsm).

I can now reproduce some sdcard-issues, looking into it.
[Motorola Droid 4] rruleford:
Well thank you my friend. Seemed like a reboot into recovery and dalvik/cache wipe fixed it anyway. Any news about getting ART to work? No pressure just curious to give it a try.
[Motorola Droid 4] huckky:
ART is working for me quite good. And honestly i couldn't believe my eyes first time opened an app with art. that was FAST.
[Motorola Droid 4] rruleford:
What gapps package did u use? All the problem seems to lay in the gapps force closing when switched to ART
[Motorola Droid 4] huckky:
cm-11-20131119-UNOFFICIAL-maserati.zip with

pa_gapps-full-4.4-20131119-signed.zip 257mb file.

i will try 20131123-2 tomorrow. hope that fixes sdcard for me.
[Motorola Droid 4] rruleford:
Its really weird that I saw these SD card issues constantly on cm10.2 but not a single problem with it on this build. The only way I could fix it was to reboot recovery and wipe dalvik/cache. :-/ well hope it does fix it with users seeing this issue. Only thing missing now is screenshot on power menu.
[Motorola Droid 4] rruleford:
Ok so I went to take a pic of the pretty snow on the mountains and still saving as gray screen buttttt when I choose to take photo when sharing via MMS or Facebook it works just fine. On 11-23 build.
[Motorola Droid 4] lucize:
the only thing I got in catlog is

W/AudioTrack( 131): obtainBuffer timed out (is the CPU pegged?) 0x40055270 name=0x2user=00000d80, server=00000000

dmesg is clean.

now I'm testing without hdmi.

I only said about cpcap because all things are related to it

hopefully you can fix the sensors if they are the problem, but I think that when I was playing with the clocks and opp the sound issue appeared very quickly.

regards

Lucian
[Motorola Droid 4] stargo:
Hmm, not really helpful.

One thing to remember is, that the userspace audio-part is a binary-blob from motorola. So if it's related to that, we have a problem :(

Let me know if it works.

Let's hope it's not cpcap.

I've pushed the sensor-fix to my repository and into CM.

What could happen was that the phone could enter deep-sleep while the sensor was executing its interrupt-handler and transferring data on the i2c-bus.

EDIT: now I see why you mention audio, but with SOD I mean sleep-of-death...

Regards,

Michael
[Motorola Droid 4] stargo:
Did you by any chance have your hand near the proximity sensor? Rapidly switching on/off and blocking the proximity sensor is exactly what would cause the problem. I know why I couldn't reproduce it, I'm always switching the device on with the hand I'm holding it in, so I'm not obstructing the proximity sensor...

No real clue in it :(

But I'm hoping that the patch fixes the problem ;)

(This is actually from the stock-kernel, but gerrit seems to have eaten my [moto]-Prefix from the patch)

Regards,

Michael
[Motorola Droid 4] lucize:
could it be the way I pressed, because for me it happened only when I pressed the power button to wake up the device and in very rare occasions.

Regards
[Motorola Droid 4] Shobai:
WiFi?

Hey, a quick question: I'm on the current nightly, 140217, and I can't for the life of me get the WiFi to turn on =/ It sits there "Turning Wi-Fi on..." and never changes, and the toggle button is greyed out. Any suggestions? I did a factory wipe from safestrap after the first boot on 0217 was successful, and only noticed it after that...

Also, I have still been having the suspend_backoff issue.
[Motorola Droid 4] stargo:
Run wifical.sh

Did it start again on the 0217-build or was it there on the previous ones, too?

I've reverted most of my USB changes in that build to fix a crash of the USB host-controller where you lose the mobile connection until you reboot the phone. If you had the problem in previous builds too, this would indicate that the problem is in a different area, which would (hopefully) be safer to touch :)

Thanks & regards,

Michael
[Motorola Droid 4] lucize:
so disabling hdmi seems to be a good ideea

the battery was at ~50% when I flashed the modified one and now I have a very good battery life, didn't had this kind of standby with CMx ever

until now everything seems to be ok

edit:

maybe disabling for the framebuffer too will help more
[Motorola Droid 4] Shobai:
Ah, I now remember seeing something a little while back about wifical.sh; I ran that and after a reboot it's working again, thanks.

As for the suspend_backoff thing, I think I've seen it in every nightly I've tried (which is basically every 3rd or 4th, at least, since I became aware of them). Having said that, there are a couple of things at my end that have me wondering: My digitiser isn't working when the keyboard is slid open, although the phone often remembers the last touch when I slide it closed. Secondly, I've been using the OTA nightlies to install in place, without wiping - this [0217] is the first time I've done a factory reset, via safestrap 3.63, since I discovered the OTAs.

So, I'm wondering whether the reset will solve anything, whether the [seemingly] hardware issue with the touchscreen is affecting things, and also whether the safestrap version is affecting things. So, having wiped and updated safestrap, I guess now I just wait and see whether it crops up again.

In other news, the kernel Lucize has posted seems like an interesting option: even if I can't get suspend_backoff to go away, if I can drop the CPU state from 300MHz down to 100MHz it might still save a bit of battery. Just gotta wait for the response as to how to install it, I guess.

Thanks again for your work!
[Motorola Droid 4] stargo:
Just one short remark, as I have no time...

You are using Safestrap 3.63? Please update to 3.65, as it fixes some hw-init problems.

Regards,

MIchael
[Motorola Droid 4] lucize:
just install it in safestrap over the current slot, do you have 3.11 ? I tested it only on 3.65 or you can download the rom image and overwrite the files and after that flash the image

Regards
[Motorola Droid 4] IndiaBhai:
Hey there guys I'm having a weird issue with battery drain and sd card usage with the 2/06 build (unable to update due to the SD card issue)

1) The battery will drain a lot and die much quicker than it did with stock and 10.2 builds. Oddly enough, when I plug it in for charging after it dies, the phone reports that it has 40-60% battery remaining. Is the ROM just calculating battery usage incorrectly and dying based on that?

2) I cannot download or attach any files from any app. The internal SD card is reporting as being read only and the ROM doesn't seem to be able to tell apps to direct to the external (though I am able to save pictures to the external)

Any ideas/help? Sorry for the long post.

- Ayush
[Motorola Droid 4] rush242:
Old [SYM] symbols

Hey All,

In older (OEM?) ROMs the [SYM] button brought up a significantly larger selection of symbols. Is there a way to revert back to the original, or replace the current one with the old one?

Thanks, in advance.
[Motorola Droid 4] Shobai:
Thanks, I have since done so [I snuck it into the para under the one you quoted, but neglected to specify that it was 3.65 I'd updated to].

OK, so using 3.65 I flashed it straight onto the slot. Do you recommend a factory reset after doing so? Or will it be fine to keep it running as is?

Finally, I'd like to +1 rush242's suggestion - what's involved in getting the extra symbols back?