yashsingh1/xdaforums huggingface dataset:
[RAZR HD Android Development] iBolski:
Yeah, I've done that and then I can't even get connected to my cellular data without going back to stock and then clean flashing CM12.

What I did was flash back to stock again, re-established a GPS lock via my Google Maps and then clean flashed 12/02 and it seems to be working now. Not sure why it didn't before.

Also, it appears to be restarting my radio much faster than before. I guess clean flashing is the way to go. Too many dirty flashes from previous nightlies might have caused some issues.

Thanks for the tips, though.
[RAZR HD Android Development] Zeljko1234:
As described, I had problem with dirty flash. For time to time is good idea to clean flash, especially when devs are changing a lot.

I'm glad that works for you again. Do you have feeling that works smoother?
[RAZR HD Android Development] niksy+:
Clean flashing the 2nd December build (format /system /data /cache) boots up fine and gets HSDPA straight away, but then freezes on the second step of the setup - at the WiFi screen. I guess WiFi driver causes kernel panic and the whole thing crashes... Just a guess, though. Nobody else experienced this?

Damn it... The 1st December build, on the other hand, booted up fine, but there was no signal after many many many reboots and no matter how many times I switched network types or aeroplane mode.

Will wait for a build or two until trying again, I guess. Thanks to all our active devs, you guys rock :)
[RAZR HD Android Development] Zeljko1234:
Try to shutdown, wait for phone to cool down, try to boot again and just wait. Last night I couldn't get signal and then I just left phone and after few minutes signal appeared.
[RAZR HD Android Development] drtweak:
Yea think I will just wait till a more official build comes out. Running 11/24 without almost any issue. Started to get a few stop responding on programs. Messenger stopped working all together (switched to hangout. Been avoiding it all this time. Didn't realize how great it was now that i use the Google voice dialer since magic jack doesn't work on 5.0) and the fact HDR crashes on the camera every time. Other than that I love Lollipop. Can't wait for my Droid Turbo and for it to have Lollipop. Just hope it gets rooted.
[RAZR HD Android Development] Not_A_Dev:
That's very true! I decided to clean-flash the 12/2 build after I had dirty-flashed the previous 7 or 8 nightlies, and what a difference that makes. Nova Launcher doesn't freeze up/fc any longer, and the whole experience is just snappier. I can't believe this is an alpha version. I've been using it as a DD for the past 2 or 3 weeks.
[RAZR HD Android Development] yujikaido79:
atrix lapdock

I haven't tried HDMI output to my tv but I have used my atrix lapdock that was working great full screen with stock kitkat, 5.0 not so much. Same issues as previous CM builds large black borders on top and bottom of screen.
[RAZR HD Android Development] djvita:
Clean flashed 12/02 everything works
[RAZR HD Android Development] nagim:
Thanks for the reply!

So this could be a CM issue rather than a Lollipop issue?

Also, layout hasn't changed, right? Still only mirroring?

Thanks again!
[RAZR HD Android Development] niksy+:
Reboots, reboots, reboots...

Huh. Seems that my issue is bigger than I thought it is at first.

I just tried clean flashing (CM11 -> CWM 6.0.4.9 -> format /system + format /data +format /cache -> install rom + gapps zips) the previous build again (11/30) and it resulted in the same thing. The first step of the initial setup shows up, the signal icon shows up full, with a H+ indicator, I select the language, then to the next step and the phone hangs there for a few seconds and then reboots. It freezes as soon as the "Turn on your wifi something" screen shows up. After rebooting the first time, it goes into a bootloop and never reaches the system again.

Then dirty flashed the latest (12/02) build - the first boot went into system, straight to the lock screen without the initial setup, but it hanged right there and rebooted after a few seconds and again went into a bootloop. Now flashed back to CM11 and all is completely fine. I'm a bit puzzled, to be honest.

Any suggestions on debugging this? The 11/30 built previously worked stable, but without any network signal. I'm thinking about switching to the latest TWRP or perhaps restoring the 4.4.2 backup and then going to CM12 straight from there and see how it goes.

What do you guys mean by a clean flash, formatting all partitions or just wiping data+cache? :rolleyes:
[RAZR HD Android Development] jewbydoo:
I suggest bumping up to 11/29. I had the same problem with the messaging app, it would crash whenever it got a text message. not only that, it wouldn't even store the text message that it received, effectively completely losing the message someone was trying to send you.

The 11/29 build completely fixed this and it is the best one by far. I suggest flashing up to 11/29 and creating a backup in your recovery.
[RAZR HD Android Development] lcc014:
Okay. Thanks for the info.
[RAZR HD Android Development] palmbeach05:
Speaking of changes, latest update on stagefright detector came out. I know i'm still sitting on CM11 atm, but zimperium's app is reporting the CVE-2015-6022 vulnerability. There is one that shows up for CM12 and up as well (from what i've read online). Patches should be pushed out shortly, right now they're hitting the Nexuses, haven't seen the actual patches yet. Just giving you the heads up about that in case you weren't tracking it.
[RAZR HD Android Development] CWGSM3VO:
Newer CM12.1 now shows security patch level, came about last couple of builds (edit: 10-8 was the appearance of the patch level in settings but the patches for the CVE came earlier and I can't seem to find the commit against it)

http://www.kb.cert.org/vuls/id/924951

http://review.cyanogenmod.org/#/c/111118/

http://review.cyanogenmod.org/#/c/111123/
[RAZR HD Android Development] palmbeach05:
1 Oct was the possible patch date i was seeing as well on my end for the latest round of vulnerabilities. Thanks for that info about it being patched
[RAZR HD Android Development] amedeh123:
Running 9-10 for a full day. No flashing to black anymore. Calc bug seems to be gone too.

Good times.
[RAZR HD Android Development] Zeljko1234:
CM13? :p
[RAZR HD Android Development] palmbeach05:
Github showing CM13 branch on the CM side of things, no CM13 branch on xt926, xt925, or mb886
[RAZR HD Android Development] md07:
very bad news. I always like design Razr HD very much, and i want CM keep support CM13 for this model :rolleyes:
[RAZR HD Android Development] palmbeach05:
Very bad news? What i reported was normal for any device after a major update such as the LP to MM update. Patience is needed, or immediately jump to one of the Nexus devices and deal with the complications with root.

EDIT - see link below for reasonable expectations on CM13

http://www.theandroidsoul.com/cyanogenmod-13-cm13-and-android-6-0-marshmallow-update-84796/
[RAZR HD Android Development] md07:
so, do you think Cyanogenmod support CM13 for Razr HD?
[RAZR HD Android Development] palmbeach05:
Its up to the maintainers. I'm not sure if you have a jbbl or a kkbl, but i know that devs who are maintaining both frequently are on here. That question would be better suited to be asked to them. C, epinter (if he's still active), Z, kabaldan, and others would be the ppl to go to. Start with C and Z since they're always on here.
[RAZR HD Android Development] kabaldan:
- cm-13.0 is currently in a very rapid development phase, it doesn't build yet even for well maintained, more current devices (unless tons of cherry-picks, hacks and manual deleting of targets that don't compile yet is done)

- there's no A-family HALs' M source available from CAF (yet? let's see if there will be a release for msm8960 at all) - https://www.codeaurora.org/xwiki/bin/QAEP/release

=> it'll take some time to see how moto msm8960 2012 can cope with M

I'm pretty sure I'll be trying to get cm-13.0 running on moto msm8960 2012 devices, but please don't expect too much any time soon.

I'm busy as hell with life/family/work.

btw: I'm looking for a screen replacement for my xt925, so I don't cut my fingers when using it - https://plus.google.com/+PavelKucera/posts/ZYepoYfB2Vu (yes, the touchscreen fortunately still works despite the glass cracks). If someone has a bricked (or otherwise damaged, but screen OK xt92x device), I'd welcome to get it for the spare parts...
[RAZR HD Android Development] palmbeach05:
I figured this time around would be a bit harder to do a wk into things. I've stepped away from monitoring the updates here and have been focusing on things in the realm of chainfire. They're having...fun...with that issue, and thats just on stock Nexus OTAs.
[RAZR HD Android Development] md07:
ok ! keep working!

PS: find a screen on ebay, cheap price
[RAZR HD Android Development] insanix:
really NOT cool PS
[RAZR HD Android Development] Zeljko1234:
Not so long ago I [MENTION=4442286]niksy+[/MENTION] found device on swappa for $30. He sent me money via paypal, I bought device and sent to him. Postage was about $15. We can try the same for [MENTION=2218140]kabaldan[/MENTION]. ebay is also option with costs covered by us.
[RAZR HD Android Development] niksy+:
That being said, I can't find a sub-$100 DROID HD device on swappa at the moment :/ Anything cheap on ebay, or is a full front display the best option?

And is anyone up for a quick fundraiser? :) I'd be very willing to chip in.
[RAZR HD Android Development] amedeh123:
Theres also the option to get a brand new display, without wear and without burn-in.

It shouldnt be that much more expensive, and it would be ideal in case you decide on a fundraiser.
[RAZR HD Android Development] Zeljko1234:
What about sending your broken display? If is functional with just "spiderman" edition and not cutting fingers.
[RAZR HD Android Development] niksy+:
It's 100% dead, Z :( Doesn't even turn on, and the HDMI out shows that it registers no touches. And I'm pretty sure that I already told you this :D
[RAZR HD Android Development] Zeljko1234:
Yeah I remember, let's blame jet lag :D

Anyway, could someone explain those two commits?

http://review.cyanogenmod.org/#/c/112836/

http://review.cyanogenmod.org/#/c/112624/
[RAZR HD Android Development] IronTechmonkey:
I suffer pedestrian lag but only if I walk fast :).... and have been pondering those same commits from my Moto E. Looks like quark + antiquark = 0 change in mass but I cannot tell the meaning of the code that was added then removed.
[RAZR HD Android Development] CWGSM3VO:
I believe it's reference to this:

https://source.android.com/devices/tech/power/index.html

Which as I recall, is handled in Frameworks as Steve K said. I *believe* this is the stuff you see in init for battery profile modes (conservative, balanced, performance) however, if this is what he's referencing, it doesn't seem as versatile which leads me to believe there's more to it than I see/understand.

The basic idea is to trigger actions based on battery level/profile -- for example, in conservative, you might not want WiFi/GPS enabled, so, it would disable these services when that mode is triggered.

Unfortunately, a lot of the newer devices have special attention paid to them for power*.c in the kernel -- one of the things I wanted to get around to (and still haven't) was adapting something like msm8994 or 8912 (or whatever) power profiles to 8960 so we can use some of the goodies too.
[RAZR HD Android Development] Zeljko1234:
Don't change time zones when you walk fast, you Flash :D
[RAZR HD Android Development] Zeljko1234:
http://www.cmxlog.com/13/ :)

[YOUTUBE]PK1MBnGs4RU[/YOUTUBE]
[RAZR HD Android Development] md07:
:silly:

i search in that, can see msm8960 inside....... So.....==>------
[RAZR HD Android Development] Zeljko1234:
As the first song tells:

Is this the end of the beginning?

Or the beginning of the end?
[RAZR HD Android Development] rahimali:
That msm8960 is preceded by htc (android_device_htc_msm8960-common) so probably doesn't even apply to our devices, maybe for HTC One S or X or some such...
[RAZR HD Android Development] CWGSM3VO:
There's no 8960 HAL for 6.0 yet, as [MENTION=2218140]kabaldan[/MENTION] pointed out:

https://www.codeaurora.org/xwiki/bin/QAEP/release

I'm sure someone will try to get the 5.0 HAL working for 6.0 first until one becomes available for 6.0
[RAZR HD Android Development] Thibault1171:
Hi guys, I'm still on 09/21 official build (clean flashed). I plan to update. What's best for now? Latest unofficial build by C, any official nightly, latest snapshot?

If I install latest C's build, must I manually do the tricks you were talking about in terminal ?

Thanks ?
[RAZR HD Android Development] rahimali:
According to the developer in the BlissPop thread, our devices will be getting Marshmallow update and consequently BlissROM (BlissMellow?) for all Razr devices except 925....
[RAZR HD Android Development] Zeljko1234:
Are you kidding us? 925 and 926 are almost the same.
[RAZR HD Android Development] rahimali:
Sorry 925_JBBL and I'm just quoting the dev here... :D
[RAZR HD Android Development] Zeljko1234:
This is for ban, at least :D
[RAZR HD Android Development] rahimali:
Nooooooo! :D
[RAZR HD Android Development] Zeljko1234:
Maybe if you post link of the bliss topic about marshmallow ;)
[RAZR HD Android Development] rahimali:
Never again! :D
[RAZR HD Android Development] Zeljko1234:
Link or ban! :D
[RAZR HD Android Development] palmbeach05:
Lmao at blisspop mm debate above. I needed a laugh to start my day
[RAZR HD Android Development] CWGSM3VO:
https://plus.google.com/101993990944923379207/posts/iTfQrDyPMAV

Yeah, I'll be giving BlissPop a pass, yet again...
[RAZR HD Android Development] rahimali:
C, I remember the "A Better Camera" issue had been raised earlier also and the Bliss developers have clarified that it's included with the express permission of the developers of said app. I don't remember if that clarification was here in XDA or DroidRazr forums...

Regardless, the fact that BlissMellow will be available just means that Marshmallow source will be available for our devices...
[RAZR HD Android Development] CWGSM3VO:
Fair enough. But this particular ROM/team has had controversy before (as it were, internet soap operas). I'm not involved enough to pick sides and someone may just be seeking headlines (so to speak) but enough gotchas do sway public opinion (such as mine).

It may indeed mean that M may become available for our devices.
[RAZR HD Android Development] Zeljko1234:
Are they gonna support iP too?
[RAZR HD Android Development] CWGSM3VO:
I could be wrong here but last I saw, they use CM's device tree(s) for their builds.
[RAZR HD Android Development] Zeljko1234:
Didn't know that CM supports iP(hone) :D

Yes, I'm bored :D
[RAZR HD Android Development] CWGSM3VO:
You kids and your internet lingo...
[RAZR HD Android Development] IronTechmonkey:
Howl. I just stated in a post ."...you crazy kids get off my lawn..." Hang in there Pops.
[RAZR HD Android Development] md07:
Blisspop have a bug which not ever fixed: ringtone and notification sometime not play
[RAZR HD Android Development] CWGSM3VO:
http://review.cyanogenmod.org/#/c/113127/

This is cool and may make ambient brightness useful again.
[RAZR HD Android Development] md07:
:good:
[RAZR HD Android Development] IronTechmonkey:
Cool indeed. Will be testing this over weekend. Thanks for the tip and pardon the cross ROM chatter but this one may be applicable here and on my Moto E (as it was on my now dearly departed AHD). Auto-brightness is indeed glacially slow. Also I think there was a recent commit, or perhaps incidental change, that made the dimming less aggressive in terms of brighness value rather than reaction time, which I noticed behaviorally on the device about 2 weeks ago. Before then Auto-brightness was more frequently using the 1% - 7% range that the system usually does not use. Now that the dimming was made less aggressive that lower range is still used but less frequently and I think the lower limit was raised from about 1% to 2% where in older ROMS it was about 7% - 8%. These percentages are calculated from the x/255 values actually used by Tasker and the system.

BTW Incidental to what Z once called Borg (I was sooo honored :))

I've used this tasker scene with brightness slider and several manually set values, and the native brightness variable, to determine the system's perceived lowest value which seemed have been about 8% (20/255) for everything in Kitkat but now still is about 8% for some things and 2% (5/255) in the native brightness slider. The recent change I referred to seems to have changed that minimum from 1% to 2%. One potential downside that I hope does not occur is higher battery drain due to more aggressive tracking and reaction.
[RAZR HD Android Development] CWGSM3VO:
Noticed today that [MENTION=264678]kab[/MENTION]ldan is working on msm8960_jbbl for CM13 :)
[RAZR HD Android Development] Zeljko1234:
jbbl?! It was expected to get cm13 for kkbl first, jbbl not so likely. But it's nice to see that he's working on cm13 for any of msm8960 family :)
[RAZR HD Android Development] CWGSM3VO:
Guessing he's getting his xt907 going first :)

EDIT: Sorry, xt897? Not sure, but look here: http://review.cyanogenmod.org/#/c/114402/
[RAZR HD Android Development] kabaldan:
I have two Photon Qs (xt897) and one Razr HD (xt925). One of my Qs is my daily driver (running cm12.1) and the other one (with badly broken screen since the late august accident) is where I actually do the cm13 bring-up (using usb mouse to circumvent the dead TS).

The bring-up of the jbbl device that's still on 3.0 kernel is much bigger challenge (= more fun) than the easier path with xt925 on 3.4 kernel. So that's why I started with xt897. I'll move to kkbl xt925/6 cm13 bring-up as soon as my limited free time to play with phones will permit.
[RAZR HD Android Development] palmbeach05:
I like how this guy thinks. Bigger challenge = more fun :D i know what you mean by that thinking, i'm the same way.
[RAZR HD Android Development] amedeh123:
Well... this is the guy who brought JB to the Moto Milestone (600mhz cortex a8 and 256mb of RAM). And it was actually useable.
[RAZR HD Android Development] amedeh123:
Btw, what is the preferred persistent method of changing minfree values on the RHD?

Apps are closing a lot on the background and I want to play with it a bit.
[RAZR HD Android Development] CWGSM3VO:
Minfree values are set at source level, if you browse the commits, you can find the one [MENTION=3721576]epinter[/MENTION] did where he set it. You can change it on a running system but frankly, this problem was dealt with a long time ago. If you're getting apps closing either you're running waaay too much (overloading the device) or you have some seriously hungry apps.

EDIT: Search this thread for my "perf" shell script, I set minfree (among other things) in it. It'll get you started in the right direction.
[RAZR HD Android Development] IronTechmonkey:
in regards to the recent auto-brightness tweak... lets just say I hope it works better on your hardware than mine

With the 10/20/15 tweak auto-brightness now responds quicker but dives deeper even in moderate light. As I am writing this it is adjusting too frequently and deeply for the constant lighting it is in. Under a bank of long multi-bulb fluorescent light fixtures spaced 4 feet apart in all directions, even a slight change in orientation of the phone results in a large change in brightness and it stays too dark too much of the time; and this is coming from someone who's default brightness value is 4%! One problem seems to have been replaced by another. I can see an attempt to achieve lower average brightness over time and faster response somewhere in this tweak but the result is "just turrible" (to quote The Round Mound Of Rebound).

The 10/20/15 tweak seems to have dropped the lower limit used by auto brightness back down to 1% or even lower. The native brightness slider in Quick Tiles hits a minimum of 5/255 (about 2%) but the lowest value being used with auto-brightness enabled is noticeably lower - probably approaching an absolute minimum less than 1%. Since, with auto-brightness enabled, the system incorrectly reports the previous manually set brightness value into variable I cannot get a # for it but the effect is quite noticeable. Also, those lower values are used in much brighter ambient light than before. I kind of like that but expect most people would not.
[RAZR HD Android Development] Zeljko1234:
I remember, GB based CM (CM7?) has nice menu to set all thresholds for auto brightness. Would be awesome to get that feature again.
[RAZR HD Android Development] IronTechmonkey:
I got in the game after that but it sounds nice.
[RAZR HD Android Development] Zeljko1234:
Editable file would be good enough too. Maybe there's or everything is hard coded.

I still have Atrix 4G and few screenshots how those setting look like.
[RAZR HD Android Development] CWGSM3VO:
Is LiveDisplay enabled for these tests? I have mine enabled @ automatic. Automatic brightness does seem faster but now that you mentioned it, it seemed dim this morning when I got up @ 6am (close to winter here, so it would have been still dark outside).
[RAZR HD Android Development] IronTechmonkey:
Livedisplay is off (as part of my post flash routine). Digging deeper; auto-brightness now seems to be using the same absolute minimum in situations including: near total dark, low indirect cfl (60w equivalent), medium indirect natural light indoors, and thumb over sensor - no adjustment until under brighter light. Even with darker backgrounds and themes and their resultant higher contrast it it seems too dim in all of those situations except nearly full dark. I wish there were a way to get actual brightness level while auto-brightness is enabled.
[RAZR HD Android Development] CWGSM3VO:
I played with this today (with LiveDisplay enabled, automatic, I like it what can I say) and noticed that when I moved from light to dark and vice versa, on my device, the brightness scaling adapted rather quickly and noticeably smoother than I'm used to with ambient lighting enabled. For me, the experience is choppy in appearance normally.

It's not scientific and requires more subjective playing with my device but there you have it :)

EDIT: For me it's really noticeable when launching gmail, once inbox is displayed the brightness will scale nicely and smoothly compared to what I'm used to. Same with screen timeout as it slowly blacks out.
[RAZR HD Android Development] amedeh123:
Im not using many, mainly chrome stock email and whatsapp. and the only background app I got running is whatsapp. Thats why I want to mess with it.

Will search for your script anyway and see what comes out of it, thanks.
[RAZR HD Android Development] IronTechmonkey:
Well, thanks to your feedback and some more testing on my device there seem to be big differences across different hardware (which really isn't a surprise). This is a disaster on Moto E. The one thing I used auto-brightness for was to get brighter screen for brief periods when outside and it is no longer even useful for that. Autobrighness (on MotoE) now hugs lowest possible value of about 1% until under very bright and direct light, and it never makes the display bright enough to be readable until under direct sunlight. I explored the livedisplay settings a bit which, although nifty, did not mitigate the auobrightness issues. This is the worst autobrightness combination I've seen in 3 years of droiding on 2 devices in dozens ROMS... but I'm glad it's working for you in the great white north (Take Off!) and I'll take further grousing about it to the moto E thread. Grazie mille.
[RAZR HD Android Development] IronTechmonkey:
Those look nifty. At this moment I wold not mind being able to control the lower limit trigger.
[RAZR HD Android Development] Zeljko1234:
I don't know why this feature is abandoned after CM7. It was possible to control everything related to auto brightness and after few days of experimenting everyone was able to find the best settings.