Develop Bugs

[Q]CM10 Flinny Test build

Hi XDA,
I'm currently running latest Flinny CM10 test build (125), and an issue I've had for a while is that even when the phone is locked, but screen is on, I can pull down the notification bar and do actions. Is this normal? Is there a setting somewhere that needs to be switched off? I am using Apex launcher.
Cheers.

As far as I know this is a standard behavior since android 4.0 (ICS). There is no settings to disable it.
Someone correct me if I’m wrong
EDIT: If you have enabled screen security (pattern, PIN, password) you should not be able to pull down the notification bar. You should be able to pull it down only with slide lock.

I enabled a simple gesture unlock and yes now I can't pull down the notification bar.
It still seems strange that this is normal behaviour.
Thanks heaps!

yup... That's normal...
I also face some issue which is the ROM could not connect to external gps device... I think that's issue exist in CM10 since have same issue with galaxy smtd...

Yeah I don't have working orientation, light or gyro sensors still. It seems like some people have this problem and others don't depending on hardware revision.

Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010

Vauvenal7 said:
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Click to expand...
Click to collapse
Just wondering... Do u install gapps? If not, you should do that when u install it for the first time (after you install the rom).

Vauvenal7 said:
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Click to expand...
Click to collapse
As with every CM build after 4.1.11.1 on the G1, ALWAYS FLASH GAPPS AFTER FLASHING THE ROM.

cm made a 4.2 donut where the base was flashed first still, so starting with eclair gapps where flashed after
Sent from my HTC Vision using xda premium

blackknightavalon said:
As with every CM build after 4.1.11.1 on the G1, ALWAYS FLASH GAPPS AFTER FLASHING THE ROM.
Click to expand...
Click to collapse
I did, yet ther was no camera app pre installed
Even the icon on the unlock streen existed, but when i unlocked it with the cam symbol nothing happened, it just went back to the lockscreen
I had mimicry before and therefore i got used to flash gapps, so did i with this jb rom too
Sent from my GT-N8010

I love this ROM, everything I generally use on a regular basis works fine. My only real problem is this ROM is a serious power drain, within an hour of being unplugged in the morning I have already lost 10% of the battery, by mid afternoon I am forced to plug the phone back in, this is something of an issue as I work at hospitals and plugging appliances into the mains is a violation of health and safety regulations, but I need my phone so I do what ya gotta do. Is there any way to reduce the drain from this ROM as I am fairly sure it is not any applications I have installed causing it, as none are running in the background when I check running apps.

plug it in to a computer with a logcat running, see what is going on that way. or if you aren't able to sit in front of a computer for a while watchdog is a nice app for this (keep in mind it should be for testing basis and be removed later as it to will always be running in the background)
Sent from my HTC Vision using xda premium

evernote makes phone slow
I am using this rom (build 124) and I have and after restoring all my apps it became really slow. After some try/error I found that uninstalling some apps solved the problem. After that I started installing my apps again one by one and I found installing evernote make the phone near unusable.
Anybody is experiencing this? it also happen if I install "camera 360".

I am running build 127 of this ROM which definitely seems faster than build 126 which was the first one I tried and seems to be quick enough to actually use it most of the time.
When things do go slow it seems to be when switching to a new app and seems more likely to happen is the new or old app is big.
Regarding more apps slowing things down I wonder if it is actually more widgets and background services. If this is, as I suspect, do to with how many apps can be cached in RAM for fast switching then the more apps have something running in the background, for example to sync with a cloud service or to keep a widget updated, the less RAM there will be for the apps you are trying to use and there will therefore be a greater chance the app you are trying to start has to be started from scratch.

These threads really need to stop, Flinny's test build is just that A TEST BUILD problems/issues are expected.

I think it's normal...anyway it don't obstruct me

tarroyo said:
These threads really need to stop, Flinny's test build is just that A TEST BUILD problems/issues are expected.
Click to expand...
Click to collapse
In my case I am certainly NOT contributing in order to criticise. Of course I know a test build may have issues but, like many others I suspect, I am happy to try the latest thing. When things don't work quite right it is worth discussing it. If we can understand what is happening we can help each other mitigate the issue and maybe even have something useful to feed back to developers.
I was running build 127 and things had become very slow. I have now updated to build 128 and the phone is fast again. At this stage I am not sure if this has anything to do with the new build or whether it is down to apps. I have all 45 apps installed but for many of those that sync to cloud services I have not yet got round to setting up the username/password for that to happen so this may be limiting the amount of background activity to a level where it doesn't get in the way. I'll try setting some of them up and see what happens.

For those having unresponsive touch screens with 4.2.1 (as opposed to SODs)

https://www.youtube.com/watch?v=x92uTTdxglI&feature=youtube_gdata_player
As soon as the latest firmware hit I've tried all the roms and they all would end up with a unresponsive touch screen. No matter what kernel and rom, I'd have to do a battery pull, it could be less than an hour or around two days of uptime. It was weird because you can see PGM works fine. After countless of lock ups, frustrated, I just mashed all my fingers on the screen and it came back to life.
I know a few of you in the development forum are coming up with this issue, hopefully it works for you.

sman789 said:
https://www.youtube.com/watch?v=x92uTTdxglI&feature=youtube_gdata_player
As soon as the latest firmware hit I've tried all the roms and they all would end up with a unresponsive touch screen. No matter what kernel and rom, I'd have to do a battery pull, it could be less than an hour or around two days of uptime. It was weird because you can see PGM works fine. After countless of lock ups, frustrated, I just mashed all my fingers on the screen and it came back to life.
I know a few of you in the development forum are coming up with this issue, hopefully it works for you.
Click to expand...
Click to collapse
Its a pgm issue man. Stop using it like I did and the problem is solved.
Sent from my Galaxy Nexus using Tapatalk 2

I thought that too but it still happened numerous times without it installed.
Sent from my Galaxy Nexus using xda app-developers app

sman789 said:
I thought that too but it still happened numerous times without it installed.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Bull****... I've had the exact same problem to the T man. If its not PGM then its another app. This is NOT an issue with android itself.
Sent from my Galaxy Nexus using Tapatalk 2

I had something similar only difference was that I had a delay in touch response, found the problem to be nova launcher switched to Holo and it went away.
Sent from my Galaxy Nexus using xda premium

Never had..maybe its because ur gnext is full of **** apps that not support android 4.2
Inviato dal mio Galaxy Nexus con Tapatalk 2

you see the status bar and the open apps in background?
seriously, no miracle that he has a stucked nexus...

Wow, way to take me as an idiot. Real friendly environment here. It's actually a documented issue and you'll see a few do have it. Some have related it to the mhz setting for screen off but that didn't fix it for everyone.
darkarvan said:
you see the status bar and the open apps in background?
seriously, no miracle that he has a stucked nexus...
Click to expand...
Click to collapse
So the greatness of Android 4.0+ handling memory well with backgrounded apps is now poopoo? C'mon darkavan, I'm not even talking about lag or slowness, the lockscreen (or as in the video, I bypassed the security lock, it didn't matter either way) would not register any touches no matter how long the screen was on.

Stop using pgm!!!!!!
Sent from my Galaxy Nexus using Tapatalk 2

yeah you are running way too much, these things take time to load. first step to troubleshooting is start off fresh with no apps (likely being caused by one of them) and see how it works.
and watching you in the video is a lot like how my parents react. When something stalls (click click clickity click click) well these mashing your fingers all over the screen get recorded. thus adding to the lag.

Alright, I give up. It didn't matter what rom, kernel, how many apps were installed. It's happened to me on multiple fresh installs without a ton of apps or even PGM. This has been an issue since 4.2.1 first came out. So I went on a tear going through multiple ROMs trying to nail down if that was the issue.
But whatever, I'm stupid and clearly have no clue what I'm doing.
(I'm actully not a novice [even if the video shows me acting like one] if you haven't picked up on my sarcasm. 4.1 and 4.2 we're fantastic as well as 4.2.1 other than this issue)

sman789 said:
Alright, I give up. It didn't matter what rom, kernel, how many apps were installed. It's happened to me on multiple fresh installs without a ton of apps or even PGM. This has been an issue since 4.2.1 first came out. So I went on a tear going through multiple ROMs trying to nail down if that was the issue.
But whatever, I'm stupid and clearly have no clue what I'm doing.
(I'm actully not a novice [even if the video shows me acting like one] if you haven't picked up on my sarcasm. 4.1 and 4.2 we're fantastic as well as 4.2.1 other than this issue)
Click to expand...
Click to collapse
Have you tried a bare bones stock google image? People run in to all sorts of odd issues when mixing and matching these custom roms and kernels. I've said it before, and I'll say it again - the stock google image is the best for stability.
The reason we don't beleive you is that you are literally the FIRST one to report this issue. It's an issue with PGM, sure, but not without it. There have been odd sleep of deaths reported, but nothing like this.
If the hardware on your device is in good condition there should be no issues here.
Install the factory image from Google, do NOT install any apps for a week, then report back here with your results.

http://forum.xda-developers.com/showthread.php?t=1776538 may be ?
you can check, in settings->developper option enable show CPU usage. it will over lay a top like output on your screen : check the blue bar (top right corner) if it's huge you fell vivtime to the same bug mentioned in the link

The 4.1.2 version is far better than the current 4.2.1 on the gnex , dunno about other devices shipping with JB on board (Nexus4)...i had used PGM on 4.1.2 and my nexus never showed a problem except the settings for PGM would be going missing and a reboot would fix the job temporarily , currently i had noticed many flaws in the 4.2.1 version that incl.s screen off delay , RAMDISK compatibilty issues (Causing SoD's +wakelocks maybe these are from the kernel) & we have to bear these small issues till we have a newer version of android , Android slows down while it installs an app since the vanilla version itself .
and for the most stable and dependable setup try Rasbeanjelly + Lean kernel these are the closest to stock with a few tweaks & patches :good: .

Ashtrix said:
The 4.1.2 version is far better than the current 4.2.1 on the gnex , dunno about other devices shipping with JB on board (Nexus4)...i had used PGM on 4.1.2 and my nexus never showed a problem except the settings for PGM would be going missing and a reboot would fix the job temporarily , currently i had noticed many flaws in the 4.2.1 version that incl.s screen off delay , RAMDISK compatibilty issues (Causing SoD's +wakelocks maybe these are from the kernel) & we have to bear these small issues till we have a newer version of android , Android slows down while it installs an app since the vanilla version itself .
and for the most stable and dependable setup try Rasbeanjelly + Lean kernel these are the closest to stock with a few tweaks & patches :good: .
Click to expand...
Click to collapse
No relevant facts, no concrete evidence.. pure heresay...
Stick with a stock google image for the time being. Most likely if you go with a 3rd party rom/kernel combination it'll introduce some other strange bug along the side.

akira02rex said:
No relevant facts, no concrete evidence.. pure heresay...
Stick with a stock google image for the time being. Most likely if you go with a 3rd party rom/kernel combination it'll introduce some other strange bug along the side.
Click to expand...
Click to collapse
Stock 4.2 is definitely more buggy than cm10 stable, cm 10.1 nightlies, and many other 4.2 ROMs. 4.2 is probably one of the buggiest releases ever. There are random reboots on several devices and many other bugs throughout the os.
Sent from my Nexus 7 using xda premium

It's the problem of PGM. Last time I also experience that. The latest version of PGM should solved it.
Sent from my Galaxy Nexus using xda premium

Woohoo CM10.1 nightly builds up !

Get em at http://get.cm/?device=p930
https://plus.google.com/u/0/117962666888533781522/posts/JCpweUi3a1h
Nz

notzippy said:
Get em at http://get.cm/?device=p930
https://plus.google.com/u/0/117962666888533781522/posts/JCpweUi3a1h
Nz
Click to expand...
Click to collapse
You beat me to it! I just saw on twitter! lol

I left my good ole Nitro at home when I got the N4 for Christmas. I'm curious for reports on the performance and stability of this rom. CM10 never really got to where it needed to be imho.

any word on the stability of the 10.1 nightly?

OMG! Just checked, thank you very much, Ricardo Queirera.

yyyyeeeaaaaahhhhh !!!!! at last !! testing this out when i get home ! will report back later ! its like XMAX all over again :good::laugh:

I installed it, seems pretty smooth. So far, it's great. I'll be hammering it throughout the day and see what I can break.

i havne't used CM's new method of updating from inside about phone, is it working well or should i stick with booting into CWM and do it the old way. If it is working well, what is the proper procedure for updating through about phone menu on CM 10 -- > 10.1

@KronicSkillz,
At the very least, I believe it'd be prudent to wipe /system and flash the newest 4.2 gapps (if you had the 4.1 gapps installed before). To be honest, though, it might be best just to back up all your app data in TiBu and do a factory reset to make sure there's no weird bugs. I've never tried upgrading from CM10 straight to CM10.1, so I couldn't tell you if you'd experience any issues. You should also have the most recent version of CWM installed because there was a point in time where it didn't play well with 4.2 (at least on the Nexus). I'm not sure if the TWRP that was kanged for the Nitro ever got up to 4.2 support or not.
Once you've gotten on CM10.1, though, the nightly updates through cmupdater are nice, but Cyandelta (available on Play Store) is better imho because it only downloads about a 10mb delta and merges it with the previous nightly's install zip instead of downloading the whole 140mb zip every day.

Is it just me or are we missing the developer options in the settings? Otherwise... This has been running 100% smoothly for the past 2 hours for me!
Sent from my LG-P930 using xda premium

Malnilion said:
@KronicSkillz,
At the very least, I believe it'd be prudent to wipe /system and flash the newest 4.2 gapps (if you had the 4.1 gapps installed before). To be honest, though, it might be best just to back up all your app data in TiBu and do a factory reset to make sure there's no weird bugs. I've never tried upgrading from CM10 straight to CM10.1, so I couldn't tell you if you'd experience any issues. You should also have the most recent version of CWM installed because there was a point in time where it didn't play well with 4.2 (at least on the Nexus). I'm not sure if the TWRP that was kanged for the Nitro ever got up to 4.2 support or not.
Once you've gotten on CM10.1, though, the nightly updates through cmupdater are nice, but Cyandelta (available on Play Store) is better imho because it only downloads about a 10mb delta and merges it with the previous nightly's install zip instead of downloading the whole 140mb zip every day.
Click to expand...
Click to collapse
I had no problems using TWRP to flash CM10.1.

Gogeta5026 said:
Is it just me or are we missing the developer options in the settings? Otherwise... This has been running 100% smoothly for the past 2 hours for me!
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
to enable developper options in 10.1, go to about phone and tap the build version till it says developper options enabled, As for the proper way to install, wipe data, wipe cache, dalvik and system ... flash 10.1 and enjoy
Sent from my LG-P930 using xda app-developers app

Edit, sorry, this comment said the same thing the post just above said

gotta say this babys pretty fast considering its the 1st nighlty build, love the drawer and homescreens transition options, very smooth. Its still missing some cool features tho (will come in next builds, well hope so..) like the lockscreen widgets and the photosphere feature for the camera that lets you take 360 degree pictures ... gotta say the keyboard is a little laggy in my case, i used to have the 4.2 keyboard on my 4.1 rom and it would run way smoother, oh well its the 1st build after all!
EDIT: Just found out the lockscreen widget are there, just figured out that you need to swipe to your left or your right on the edge of the screen on the lockscreen, awesome ! (feel a little nub i didnt find that out before)
Sent from my LG-P930 using xda app-developers app

I don't know about lockscreen widgets, but I know for a fact that photosphere isn't part of AOSP. Therefore, there's no way to really run it on a non-nexus. It's the same with picasa sync in gallery. As far as I know, lockscreen widgets are part of AOSP and there shouldn't be any issues, but I don't have my Nitro to confirm.

Malnilion said:
I don't know about lockscreen widgets, but I know for a fact that photosphere isn't part of AOSP. Therefore, there's no way to really run it on a non-nexus. It's the same with picasa sync in gallery. As far as I know, lockscreen widgets are part of AOSP and there shouldn't be any issues, but I don't have my Nitro to confirm.
Click to expand...
Click to collapse
well i know for a fact photosphere works on some device even under cm10 with 4.2 camera flashed by changing a parameter in the build.so so the rom thinks you re using a nexus and the option shows up. That being said, im confident we ll eventually be able to use this feature. :fingerscrossed:
Sent from my Transformer using xda app-developers app

i have verified with a cyanogenmod team member that it is recommended to boot into CWM manually to install new 10.x rom installs. They said once 10.1 is installed then it's safe to use the CM updater in phone for nightlies but the first 10.0x > 10.1 should be done manually.

That's an excellent news!! Unlike d*m* s*h*t LG, CM never leave us behind. Hopefully 10.1 will come with a stable kernel, instead of that crappy one as with 10

I noticed no option for Photosphere...will it flash over and work if we flash another 4.2.1 camera/gallery? Anyone try this yet? I've been running from a clean install without hitches for a few hours so I'm kinda hesitant and figured I'd see if anyone tried before I do. If not, I'll probably do a backup and give it a shot and see in the morning.

hmm, on your phones guys, camera works? on my doesn't opening, i'm using another from play store...

Have you noticed...

Everyone wants to unlock their bootloader so they can run a custom ROM, the supposed purpose being to improve performance and gain new features. But then, once they get the new ROM on there, they keep posting about all the problems they are having, and how this, that or the other doesn't work as well as stock. After goofing with every, and I mean EVERY ROM available for the Razr M, IMHO there's absolutely no reason to use a custom ROM if you are expecting "like stock" performance. It's fun, it's addicting, it can get crazy sometimes, but don't expect it to ever be "Final". More than likely, it will be abandoned the moment a new phone or Android version comes along, and you'll be left with all those unsolved FCs and "almost works" features left hanging. Sad, really.
And then there's the whole "let's take the stock ROM from some other phone entirely and try to make it work on our phone" thing. I totally don't get that. If you like the Necco Choco-Android-o-rama's OS so well, why not just buy that phone instead? I'm just sayin'...
Rooting? That's totally different. I don't know what they do in other countries for bloatware, but Verizon certainly loads up some stinker software here in the US. Tell me, unless you're really into that sort of thing, why would the average shmoe care about Zappos? I certainly don't! And, if I wanted an app for NFL football, I'm perfectly capable of picking one from Google Play, yeah? Same with all the Amazon shtuff. Yeah I get it, advertising helps cover manufacturing costs, and all that jazz. Sure they do it to every new PC from Brand Name X too, but at least you can uninstall it. So rooting is sort of revenge for hogging my limited storage space and then limiting my ability to do anything about it.
And since I'm on this rant anyway, please... PLEASE!!! No more of this "Let's see if we can make our Android look like an iPhone" crap. Or worse, "Windows 8 Phone" crap! - Ewww! That's like taking a Jaguar and trying to make it look like a Ford Pinto... you might manage it, but who the heck would want it?
This rant has been a Public Service Announcement. The thoughts and views expressed herein are not to be considered... period. :silly:

You said it!
I linked to this from my restore where I have a commentary section.

I totally agree. Don't flash ROMs if your going to complain. Its one thing to report to the devs and quite another to ***** about it. And good on ya for the entire rant.
Sent from my XT907 using Tapatalk 4

I really hope the motox stock can be ported.
It would be a big event if he & others did it.
I thank them on each post.
http://forum.xda-developers.com/showthread.php?t=2412427

I originally rooted and unlocked my bootloader on this phone because of the screen shake issue that a Motorola introduced in an update if that didn't happen I may not of rooted the phone its stock ROM has such a good layout its no wonder so many complain. I however knew what I was getting into. Rule of thumb to new flashers backups are your friend and don't piss off the developers.

I like stock... de-bloat it and its good to go... just wish I could find something to mod the navi bar... remove the recent apps button replace it with the menu button and change color of it...
Sent from my XT907 using xda app-developers app

well, the main reason why folks are not as excited about the new ROMs, is b/c there are not any ground-breaking features on the 4.2.2 or 4.3 operating systems. When I got my first android, I had Froyo. Folks were dying to get to Gingerbread in order to vastly increase performance/battery life.
the deal with Jelly Bean, is that the upgrade from stock 4.1.2 to 4.2.2 or 4.3 is minimal at best - and the changes are mostly aesthetics (although, I read that 4.3 has better bluetooth connectivity). but mostly, 4.2.2/4.3 are primarily geared towards tablets.
the race is on now to see what KitKat can bring to current phone users.
in terms of improvements, just as radorix said, these custom ROMs eliminated the shakes that I was getting on 4.1.2. so for me, while that was not a huge deal, it's enough for me to go custom.
personally, I like the tiles layout of 4.2.2 as well as the AOKP customization, so I'll stick with that for now given that my battery life/performance is stock-like.

*claps* You said it. The Razr M has actually been the first Android phone I owned where I've kept the stock ROM. I think it does fine with 4.1.2 atm, and if I really wanted a change I'd probably just theme it.

The only thing that matters to me is stability and speed. I like a fast phone and I like to o/c, push the phone. I like to test things and try to understand its problems rather than build myself because I don't have the time. If I can find the right medium between speed and stability it becomes my dd, naturally. But stock was built for a reason and every now and then I go back to 4.1.2 because I miss some of the features. Like the far left quick settings menu and Circle Clock. Why have to find a work around to add all these features and fixes to a reimagined custom OS that causes more problems when its already working? We wouldn't have anything to work with if we didn't have the source to start at!

Couldn't agree more. I've had 9 different android devices in the past 4 years. Only ones I haven't rooted are my Sony tablet s (original, don't even get me started with their abandonment of this thing, hey let's leave bugs, make a seemingly unlockable boot loader, not share any code, abandon it after realizing all the bugs exist, then support everything we make after it) and my original nexus 7. I too came back to a stock debloated deodexed ROM for the RAZR M.
Sent from my Sony Tablet S using XDA Premium 4 mobile app

JPHoller said:
Couldn't agree more. I've had 9 different android devices in the past 4 years. Only ones I haven't rooted are my Sony tablet s (original, don't even get me started with their abandonment of this thing, hey let's leave bugs, make a seemingly unlockable boot loader, not share any code, abandon it after realizing all the bugs exist, then support everything we make after it) and my original nexus 7. I too came back to a stock debloated deodexed ROM for the RAZR M.
Sent from my Sony Tablet S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol. Not the only Sammy device they've dropped. Heard of the Galaxy Player 4.2?
Oh and ezknives, you do realize the menu button is completely redundant right? Considering it pops up if needed and isn't even supported/required for Holo apps
Sent from my XT907 using Tapatalk 4

sloosecannon said:
Lol. Not the only Sammy device they've dropped. Heard of the Galaxy Player 4.2?
Oh and ezknives, you do realize the menu button is completely redundant right? Considering it pops up if needed and isn't even supported/required for Holo apps
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Not for me... with-in various apps it does not... when on different ROMs and I removed the multitasking feature and replaced it with a menu key I was able to utilize features that was other wise inaccessible... like deleting messages in Facebook app for instance... that cannot be done without a menu button or opening your browser and requesting the desktop site... I just need my menu key its never there when I need it...and I don't know what halo apps are nor use it I don't believe...
Sent from my XT907 using xda app-developers app

ezknives said:
Not for me... with-in various apps it does not... when on different ROMs and I removed the multitasking feature and replaced it with a menu key I was able to utilize features that was other wise inaccessible... like deleting messages in Facebook app for instance... that cannot be done without a menu button or opening your browser and requesting the desktop site... I just need my menu key its never there when I need it...and I don't know what halo apps are nor use it I don't believe...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Holo means apps designed for android 4.0+.
It's the ICS+ ui style. There should be a way to access the menu without a dedicated button - either built-in or by telling the system it's a legacy app that needs the settings button to appear
Sent from my XT907 using Tapatalk 4

netizenmt said:
Everyone wants to unlock their bootloader so they can run a custom ROM, the supposed purpose being to improve performance and gain new features. But then, once they get the new ROM on there, they keep posting about all the problems they are having, and how this, that or the other doesn't work as well as stock. After goofing with every, and I mean EVERY ROM available for the Razr M, IMHO there's absolutely no reason to use a custom ROM if you are expecting "like stock" performance. It's fun, it's addicting, it can get crazy sometimes, but don't expect it to ever be "Final". More than likely, it will be abandoned the moment a new phone or Android version comes along, and you'll be left with all those unsolved FCs and "almost works" features left hanging. Sad, really.
Click to expand...
Click to collapse
Meh. I disagree. I've been running CM since it went official and I haven't had any complaints. I experience much-better-than-stock performance and battery life, plus it is way more customizable. I love it!

allc0re said:
Meh. I disagree. I've been running CM since it went official and I haven't had any complaints. I experience much-better-than-stock performance and battery life, plus it is way more customizable. I love it!
Click to expand...
Click to collapse
I just tried it again. Froze on reboot, wouldn't let me into recovery, same BS as all the 4.3 versions. And I wrote the book, well thread, on how to install it, so yeah I wiped etc.
Sent from my XT907 using Tapatalk 4

i'm enjoying better than stock performance on the stable 4.2.2 branch, and i built a custom kernel for CM10.1 for better performance. I tried the 'stock' life and its boring lol. The custom ROM features and better performance are what makes it worth it in my view. 4.3 will be even better as work is continually being done on it, and it hasn't been out that long. Also, I think we need to give appreciation to the devs for giving us options as far as what we can run on this phone compared to being stuck with only one choice.

CM is getting good. Recently the "display freezing" issue got fixed, also more fixes for cardock audio and wifi. It simply takes a while to get it all done properly (with that what's left is SIM I/O and HDR (works with Moto X camera application)).
@netizenmt: Booting to recovery is not affected by the ROM you have installed, so you screwed up the installation at some point.

Skrilax_CZ said:
CM is getting good. Recently the "display freezing" issue got fixed, also more fixes for cardock audio and wifi. It simply takes a while to get it all done properly (with that what's left is SIM I/O and HDR (works with Moto X camera application)).
@netizenmt: Booting to recovery is not affected by the ROM you have installed, so you screwed up the installation at some point.
Click to expand...
Click to collapse
Would you offer a build for a Bluetooth phone user that has the SD swap working?
One that might quiet this thread?

netizenmt said:
I just tried it again. Froze on reboot, wouldn't let me into recovery, same BS as all the 4.3 versions. And I wrote the book, well thread, on how to install it, so yeah I wiped etc.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
There are a few tricks to getting 4.3 installed and running but it will never happen if u just quite and go back to stock before u get it up and running correctly. I had a terrible time getting 4.3 to boot, keyboard forcing close, stability etc but I figured all that out and wouldn't think of going back to stock. The amount and way if partions the internal drive alone will keep me from ever going back to stock.
Sent from my XT907 using Tapatalk 2

stanlalee said:
There are a few tricks to getting 4.3 installed and running but it will never happen if u just quite and go back to stock before u get it up and running correctly. I had a terrible time getting 4.3 to boot, keyboard forcing close, stability etc but I figured all that out and wouldn't think of going back to stock. The amount and way if partions the internal drive alone will keep me from ever going back to stock.
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
You actually just made my whole point.
While it's cool you had time, patience, skill and effort to resolve your issues with 4.3, that's not the point of this thread. So do I. The point is, if you think you're going to slap one of these ROMs on and everything is going to work like stock, forget it. If that's what someone expects, they should stick to stock.
Sent from my XT907 using Tapatalk 4

[PORT][UNOFFICIAL] Cyanide-L for d2tmo (5.0.2 Lollipop)

All credit to this ROM goes to rogersb11. The only thing I did was change the install script so that it works on the d2tmo. With that said, this is an unofficial ROM and is not supported in any way by the original developer. That means don't go bugging rogersb11 with any questions about this. It is unsupported. It is only here so us d2tmo users can enjoy his kick ass ROM until and if there is an official port.
I will help in any way that I can, this is what I am using for my daily driver right now and I love it.
The camera does not work. I don't use my camera much, so I am fine with that for now. If you need a working camera, then this is not the ROM you want on your phone.
A few notes before install.
Thanks to rogersb11 for the Cyanide ROM, TheGeekyNimrod for the d2att port, without which I could not have done this, and leonid002, because without his assistance, I would not have even known how to do this to begin with.
First let's discuss the bugs:
The AOSP Keyboard will continuously crash on you from the first boot. Make sure you have a Google keyboard APK at the ready. This ROM comes with ES File Explorer, thanks to rogersb11, who put the ROM together in the first place, so you should have no problem installing any APKs you need to install, even before replacing the keyboard.
Install Google keyboard, then disable your AOSP keyboard. One this is done your keyboard will work just fine.
The phone will self report as the i747, that is where this ROM came from. As soon as I find what I need to change to fix that, I will update.
I believe the camera bug is still here, havent tested it yet, so just download Nexus camera from the Play store.
Other than that, works great so far.
Anyway, now it is time for the... Wait for it...
DISCLAIMER:
Despite the quality of this ROM, it is an ALPHA build.
Neither I, or any developer is responsible if you brick your device in any way, you're neighbor steals it, your nephew flushes it down the toilet, or you somehow travel back in time to an alternate 2012 where the world comes to an end in December, resulting in your phone being destroyed. Any damage to your device is YOUR RESPONSIBILITY.
You should be able to use any current Lollipop gapps with this ROM.
INSTRUCTIONS:
Download ROM below
Install a recovery if you don't have one (I use TWRP Multiboot, found in this same forum)
Factory reset (wipe Dalvik, cache, you know the drill)
Install the ROM (link below)
Install Gapps
Reboot into Cyanide
Install Google keyboard (or maybe your favorite alternative, SwiftKey works, not sure about anything else yet)
Disable AOSP Keyboard
Enjoy.
CYANIDE ROM DOWNLOAD:
1-02-2014 https://www.androidfilehost.com/?fid=95864024717074572
12-28-2014 https://www.androidfilehost.com/?fid=95864024717073794
XDA:DevDB Information
Cyanide-L Alpha d2tmo, ROM for the T-Mobile Samsung Galaxy S III
Contributors
reeferbob, leonid002, TheGeekyNimrod,
rogersb11,
Source Code: https://www.androidfilehost.com/?fid=95864024717073794
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Testing
Created 2015-01-02
Last Updated 2015-01-02

One thing I like about this ROM over CM12 is that the option to adjust your DPI is baked right in. Another is the darker theme, and the fact that you can wake with the Home button once again.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

Thanks for taking the time to port this I will check it out in the morning
Sent from my d2lte using XDA Free mobile app

Thanks OP
Downloading now
?

This thread is now opened and continue.
Edfunkycold
Have a great day!

Here's something for the webOS people: Download the app Swipe Home Button from the Play Store, and configure it so that swipe up brings up recents, and swiping far up brings up the app drawer. Do this and swap the Menu and Back buttons, and it feels that much closer to a Pre, albeit without a keyboard, and on much better hardware. I still wish I knew of a way to modify the recents so we could implement webOS 2.x like card stacks in some form. I will be trying to learn how I might be able to do that in my free time though, that was always my goal since I got an Android phone, was to try and make the UI as intuitive as webOS was. Lollipop delivered with that in a big way, but I guess I'm a little OCD and am nitpicking the small details at this point. I'm not sure how much of it is lollipop, and how much of it is from the Cyanide coder's skills, but it's snappy as hell, and definitely made huge steps towards what I wanted to see Android become.
Now just to get rid of Google's intrusiveness (because let's be honest, you lose much of the functionality of Android if you don't install the gapps) and still keep the functionality of fundamentals like the app store, Maybe a third party solution, kind of like Preware, would be the way to go about this? That still leaves the issue of fragmentation with different apps being in different app stores, however. Either way, this is the best Android has gotten for me, and I can only hope it gets even better, who knows, maybe somewhere along the way I will learn a thing or two and be able to help get there.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

reeferbob said:
Here's something for the webOS people: Download the app Swipe Home Button from the Play Store, and configure it so that swipe up brings up recents, and swiping far up brings up the app drawer. Do this and swap the Menu and Back buttons, and it feels that much closer to a Pre, albeit without a keyboard, and on much better hardware. I still wish I knew of a way to modify the recents so we could implement webOS 2.x like card stacks in some form. I will be trying to learn how I might be able to do that in my free time though, that was always my goal since I got an Android phone, was to try and make the UI as intuitive as webOS was. Lollipop delivered with that in a big way, but I guess I'm a little OCD and am nitpicking the small details at this point. I'm not sure how much of it is lollipop, and how much of it is from the Cyanide coder's skills, but it's snappy as hell, and definitely made huge steps towards what I wanted to see Android become.
Now just to get rid of Google's intrusiveness (because let's be honest, you lose much of the functionality of Android if you don't install the gapps) and still keep the functionality of fundamentals like the app store, Maybe a third party solution, kind of like Preware, would be the way to go about this? That still leaves the issue of fragmentation with different apps being in different app stores, however. Either way, this is the best Android has gotten for me, and I can only hope it gets even better, who knows, maybe somewhere along the way I will learn a thing or two and be able to help get there.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
another rom to play with thank man

In the future, I do plan to start officially building this for d2tmo. Just got a few things to get straightened out before I do. I have the device trees and everything, just gotta tie up some other ends before I dive into supporting two devices.
That said though, I will need testers as I don't own this particular device, and maybe someone to help d2tmo users trouble shoot problems that crop up specifically for their device.
Sent from my SAMSUNG-SGH-I747

Masterloki666 said:
Thanks for taking the time to port this I will check it out in the morning
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
So I've been running this all day and coming from latest nightly build this isn't bad at all still has some work to be done but its loli-goodness on our ol s3 that being said I did have a few hangs when listening to Pandora when trying to turn on screen an switch songs was at work an unable to see what exactly happened anyone else ? BTW thanks again
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

The only things I've noticed so far are as follows:
Firefox makes Metro PCS think I'm tethering for some reason, except for, ironically, when I have request desktop site checked. Opera works great though. Not to mention, if you make sure to go into the settings and put Opera on Phone mode, the look and feel of it just kind of flows with Lollipop's multitasking cards, just horizontally scrolling and vertically closing.
I heavily dislike Chrome, so I don't use it, and couldn't tell you if it works or not, because I haven't installed it.
The stock browser kind of hung on me one time, but I haven't been able to make it happen again.
The phone shuts off without warning, it seems as soon as the battery goes down to 14%
As far as Pandora, I really haven't installed it, because I have Rhapsody. I may give it a shot and see what happens.
The Firefox issue probably has something to do with the lollipop user agent, as I know that this is how Metro blocks tethering. Still weird that it works fine with the other browsers though. Anyway, due to issues beyond my control, I probably won't be online for about two weeks after today, all my bills came up due at once so my phone bill will have to wait until next payday. The extra days off work the week of Christmas really put a strain on my finances. Sure I'll probably hit a hotspot from time to time, but my phone is my main internet connection at home. Hell, it's faster than cable internet or even any DSL connection I've ever had, so why spend the extra money? I'm really surprised how well MetroPCS works in Denver, even without an LTE phone. The HSPA+ is plenty fast. Before the T-Mobile deal, I had a Metro CDMA phone, in Texas, and it was atrocious.
But yeah, I have WiFi at work so I can keep checking in from time to time when I'm out on a smoke break, plus, I'm definitely keeping an eye out for new developments.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

I just got the new build installed, the dark color scheme is awesome. I just left in the check in the installer script for the d2att this time, and added one for d2tmo, maybe it will help anybody who may be testing across multiple devices.
In this one I've noticed the AOSP keyboard is working fine so far.
I will upload it as soon as I get the chance.
If you dirty flash over the previous build, make sure when you install the new build to reinstall the gapps. After its finished wipe the cache and dalvik, otherwise Google Play services will just keep crashing.
After reinstalling gapps, wiping the dalvik and cache, I got one Google play services error, but it hasn't seemed to affect anything.
Everything about this is the same as the build from rogersb11, I just edited the install script so that it installs on d2tmo as well. Just like the earlier build, it will be unsupported. There are bugs, and on an early build, that is to be expected. But so far, I've definitely seen an improvement.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

Installed and running pretty smooth. The previous build would randomly advance my clock by 5 hours and would show all incoming calls as from "private". The new build however does none of those things.
So far on the new build, music has crashed once but relaunching it fixed that. I was not sure what nexus camera to get, not to mention their permissions were a bit crazy so I went with Open Camera and it works fine.
Thanks for taking the time to make and port this. The t999 is starting to fall to the way side and I cannot afford a new device so being able to run 5.0 is a blessing.

Working perfectly Thanks to all the devs over at d2att right How come no devs have d2tmo?? Smh.

No SIM
Hey did a clean install and the rom is telling me I have no sim inserted? Anyone else running in to this issue or have a quick fix? I tried editing APN's but it wouldnt save???

Try installing the older build first, and then install gapps, let it run it's first boot, and let everything set up. Then reboot into recovery, and install the later build, reinstall gapps, and wipe cache and Dalvik. Then boot again as normal.
This has resolved a couple of issues for me, although I haven't gotten the insert SIM message with either of these builds. Can't thoroughly test anything until the end of next week though, my phone service is cut off until I can pay my bill on the 15th, and my WiFi reception where I'm at is spotty at best (on all my devices).
Also, I am on MetroPCS, not T-Mobile, I'm just using the T999 on their network.. Which I guess is also the T-Mobile network. Not sure if there are any major differences or not.
The only issue I've had was with su, and after installing SuperSU, a couple reboots, the last one was after changing my DPI to 240, I was able to gain root access.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

jonesin said:
Hey did a clean install and the rom is telling me I have no sim inserted? Anyone else running in to this issue or have a quick fix? I tried editing APN's but it wouldnt save???
Click to expand...
Click to collapse
You may need to update your modem. I don't know about the T-Mobile modems and their availability, but for most using d2att in any LP rom, this has solved that issue.
Sent from my SAMSUNG-SGH-I747

I just installed it on my t999l. Will report back how it runs. Thanks for the ROM.

jonesin said:
Hey did a clean install and the rom is telling me I have no sim inserted? Anyone else running in to this issue or have a quick fix? I tried editing APN's but it wouldnt save???
Click to expand...
Click to collapse
I just installed the newer version, and I have the same problem. My device is t999l. Did you manage to fix the problem?

goldentequila said:
I just installed the newer version, and I have the same problem. My device is t999l. Did you manage to fix the problem?
Click to expand...
Click to collapse
Yes I was able to resolve this by updating to the latest baseband/radio. Resolved the problem immediately, I used the latest one available dated march of 2014. Hope this helps.

jonesin said:
Yes I was able to resolve this by updating to the latest baseband/radio. Resolved the problem immediately, I used the latest one available dated march of 2014. Hope this helps.
Click to expand...
Click to collapse
Thank you. I'll try that.
---------- Post added at 04:31 AM ---------- Previous post was at 04:29 AM ----------
goldentequila said:
Thank you. I'll try that.
Click to expand...
Click to collapse
OK. I encountered one major issue that was a bit scary. Everything was working fine at the first boot (except for the sim card). But, I turned off my phone. I then powered it back on, but it wouldn't boot into Android. It would just get stuck at the initial boot screen and go black. I was able to fix this by removing the battery and restarting it. If anyone experiences this issue, try that.
I tried turning off my phone to boot into recovery, and the same problem happened. I'm going to reinstall the ROM and see if the problem goes away.