Database Develop

Cyanogenmod 7 stable

Hi guys,
Correct me if I am wrong but is CM7 STABLE already out?
http://download.cyanogenmod.com/?type=stable&device=legend
AND
http://wiki.cyanogenmod.com/index.php?title=HTC_Legend
Why am I reading so many issues about GPS and various inquiries in the nightly section if there already is a stable out?

Because right now the ROM is stable but not complete that's why nightlies are still going on.

I propose an idea
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

sz1a said:
Hi guys,
Correct me if I am wrong but is CM7 STABLE already out?..
Click to expand...
Click to collapse
Yes it is, for the second time (first on 11.04 second from last night)
sz1a said:
...Why am I reading so many issues about GPS and various inquiries in the nightly section if there already is a stable out?
Click to expand...
Click to collapse
Because after first stable was out, there were still issues with GPS (in fact with the bearing during navigation). Later CM team has found a solution that was included in the nightlies, it was tested few days and most of us gave a positive feedback. Also some new things included (that "tablet" status bar was nice even if removed in #55). So, a new "stable" release was made to incorporate these.

50-3 said:
Because right now the ROM is stable but not complete that's why nightlies are still going on.
Click to expand...
Click to collapse
Nightlies are built every night and as long as the servers work they will be built every night.
Nightlies don't have anything to do with stable releases or feature completeness.

Ok, thanks. Surprised there isn't a thread dedicated to the stable release since more ppl would know about it then. I'll give 7.02 a go then, just flashed 7 stable last nite and pretty impressed so far (after new radio and the gps fix).

Has anyone experienced some minor problems with the "wake with trackpad" option in the last stable version (7.0.3)? I mean, it wakes up the device, but mostly I have to press it several times not only once.

Rapier said:
Has anyone experienced some minor problems with the "wake with trackpad" option in the last stable version (7.0.3)? I mean, it wakes up the device, but mostly I have to press it several times not only once.
Click to expand...
Click to collapse
Yes, I experienced this issue and few other. Too annoying for me, so returned back to BlaYo's B-0.8. GPS issue fixed when upgraded radio. But I ocassionally pressed something on the screen with my face during calls. After answering a call the voice was redirected to loud speaker by default (after about 1 s the loudspeaker was turned off). Automatic data synchronization (mail, news, weather) worked randomly - sometimes I had to manually check everything. I think, I just wait for fixes.

Check that your cpu speed isn't set too low when sleeping

bonesy said:
Check that your cpu speed isn't set too low when sleeping
Click to expand...
Click to collapse
CPU settings were not altered from the begining. I run at 787 with min set to 245, interactive. It is like this from the first nightly that had the CPU OC included. It's not happening allways and also didn't had such problems with nightlies or other stable versions. That's not a big deal anyways...

By the way.. no questions in Dev section..
Sent from somewhere outta space using my phone..

beastie-boy said:
Yes, I experienced this issue and few other. Too annoying for me, so returned back to BlaYo's B-0.8. GPS issue fixed when upgraded radio. But I ocassionally pressed something on the screen with my face during calls. After answering a call the voice was redirected to loud speaker by default (after about 1 s the loudspeaker was turned off). Automatic data synchronization (mail, news, weather) worked randomly - sometimes I had to manually check everything. I think, I just wait for fixes.
Click to expand...
Click to collapse
Having the loud speaker problem too, it's pretty annoying! Is it possible to revert back to 7.0.2 without wiping and just flashing?

sz1a said:
...Is it possible to revert back to 7.0.2 without wiping and just flashing?
Click to expand...
Click to collapse
Yes but won't solve the problem. This is present in all CM ROM's I've tried

Rapier said:
Yes but won't solve the problem. This is present in all CM ROM's I've tried
Click to expand...
Click to collapse
You mean CM7 roms? I didn't have the loudspeaker issue with CM6 and as far as I know it was first with 7.0.3..

And it seems it's somehow hardware dependent. I never had any "loudspeaker" problem with CM 7 stable or nightly.
regards

sz1a said:
You mean CM7 roms? I didn't have the loudspeaker issue with CM6 and as far as I know it was first with 7.0.3..
Click to expand...
Click to collapse
Yes, sorry, my mistake. I was talking only about CM7 ROMs, CM6 didn't had this

beastie-boy said:
After answering a call the voice was redirected to loud speaker by default (after about 1 s the loudspeaker was turned off).
Click to expand...
Click to collapse
Holy crap I thought I was the only one who had this. CM6 worked perfectly, since the update CM6 -> CM7.0.3 the ringtone plays, I accept the call, and can hear the other person on the (handsfree) loudspeaker for about 1 sec until the sound is switched back to the internal speaker.

It suddenly occurs to me that the reason I've never experienced this might be that I always keep the phone on "vibrate only".. Could be worth trying for those who frequently have the problem.

oysteivi said:
It suddenly occurs to me that the reason I've never experienced this might be that I always keep the phone on "vibrate only".. Could be worth trying for those who frequently have the problem.
Click to expand...
Click to collapse
I dont get it and I have the ringtone on. Some hardware version dont have it and some do it seems.

I also have the problem with background data dropping when going into sleep mode after a while. When I wake my phone up the status bar icons are all white and I have to manually check gmail, etc. The phone establishes a connection with Google services again after a while and they go back to green but it is really annoying. Didn't notice this on 7.0.2. Apparently nexus s owners are having similar problems.

SOD or something else?

OOk, so I decided to flash Slim Bean 3.0.1 out of curiosity as I know my cappy has SOD issues when not running stock GB but this seems to be different from it.
To my knowledge the SOD issues mostly involve random reboots and shutdowns. My problem is a bit different.
Now mind you up until this morning I haven't had a single issue, it's been working flawlessly. Last night I decided to grab one of my favorite battery savers, Green Power Free. Now I'm not blaming the app, it's just the last thing I installed before all this happened. I've since un installed it but now every time I lock my phone, whether it be by my lock button, Button Savior, whatever, it reboots.
The thing is it doesn't even seem like a full reboot. Instead of doing the ATT logo, then the Semaphore logo, then SlimBean logo like it normally does. It only pops up with the Slim Bean logo. It also doesn't run the media scan. Also this weird toast message "Have a nice day" has been popping up since I installed Green power and even with the un install it still persists.
I don't really think this is SOD but if it is then I guess it's back to GB for me.
If there is anymore information I can provide please just ask, I'll gladly provide you with whatever info you need.
On that note, Captivate Keep Alive doesn't work.
Sent from my Samsung Captivate via Tapatalk 2.

athdaraxen said:
Ok, so I decided to flash Slim Bean 3.0.1 out of curiosity as I know my cappy has SOD issues when not running stock GB but this seems to be different from it.
To my knowledge the SOD issues mostly involve random reboots and shutdowns. My problem is a bit different.
Now mind you up until this morning I haven't had a single issue, it's been working flawlessly. Last night I decided to grab one of my favorite battery savers, Green Power. Now I'm not blaming the app, it's just the last thing I installed before all this happened. I've since un installed it but now every time I lock my phone, whether it be by my lock button, Button Savior, whatever, it reboots.
The thing is it doesn't even seem like a full reboot. Instead of doing the ATT logo, then the Semaphore logo, then SlimBean logo like it normally does. It only pops up with the Slim Bean logo. It also doesn't run the media scan. Also this weird toast message "Have a nice day" has been popping up since I installed Green power and even with the un install it still persists.
I don't really think this is SOD but if it is then I guess it's back to GB for me.
If there is anymore information I can provide please just ask, I'll gladly provide you with whatever info you need.
Sent from my Samsung Captivate via Tapatalk 2.
Click to expand...
Click to collapse
It's a hot-reboot. The phone runs out of ram and reboots itself for safety. As you noticed, it's doesn't turn off, it simply resets everything and start fresh from being overwhelmed.
Imo, you have something draining your ram, a rogue app or a bad backup.
So first thing, did you make any changes (mods/settings)? Did you restore your apps/data? Do you have Deep Idle turned on?
Next, that Green power app seems to install more than it should on your phone, I would suggest to look into that and uninstall anything else that it installed.
Look under your Apps (in settings) to see what's running and using your ram. If you see something unusually high, stop it and might wanna concider unistalling whichever app it is, just make sure it's something you don't need. Also, look at your battery stats to see if there's something top or 2nd that isn't screen on.
Have you tried running the ROM without any restore or mods? Or even without any extra apps, just with the Gapps. I'm thinking the issue is coming from a app you're using.
Another thing that might help is to OC to 1200 and run a bigmem version of your kernel (if you don't already). But those 2 shouldn't be needed.

I've never heard of that before but now that you say it that makes complete sense.
RAM has always been an issue for me on this phone, I usually only have maybe 44 mb of free RAM. I do my best to keep it down but it's hard. I had this issue with GB as well.
As for anything involving the ROM, no. Nothing extra, I did get the Gapps but other than this I have not messed with any setting as I feel I didn't know enough to go changing anything.
I'll watch my running services for a bit and report back with my findings. I'm glad it's possibly not SOD.
EDIT:
I do believe you were spot on, I went in and cleared out my running services list and my phone isn't acting up.
Is there anything you can suggest I use to prevent this from happening again? I've seen some RAM managers and such on the market but I wasn't sure which to pick, if any.
Here is my battery stuff.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Samsung Captivate via Tapatalk 2.

athdaraxen said:
I've never heard of that before but now that you say it that makes complete sense.
RAM has always been an issue for me on this phone, I usually only have maybe 44 mb of free RAM. I do my best to keep it down but it's hard. I had this issue with GB as well.
As for anything involving the ROM, no. Nothing extra, I did get the Gapps but other than this I have not messed with any setting as I feel I didn't know enough to go changing anything.
I'll watch my running services for a bit and report back with my findings. I'm glad it's possibly not SOD.
EDIT:
I do believe you were spot on, I went in and cleared out my running services list and my phone isn't acting up.
Is there anything you can suggest I use to prevent this from happening again? I've seen some RAM managers and such on the market but I wasn't sure which to pick, if any.
Here is my battery stuff.
Sent from my Samsung Captivate via Tapatalk 2.
Click to expand...
Click to collapse
Well first off, I would get a new modem, the one you have doesn't seem all too great in your area. (unless you're in a basement or bad coverage area?)
For ram, grab Semaphore manager from the market and enable Bigmem (requires reboot and breaks 720p recording). Also, whichever extra process you stopped that were up the roof, I would highly suggest unistalling if it's not something important, like a market app (no system process eh).

BWolf56 said:
Well first off, I would get a new modem, the one you have doesn't seem all too great in your area. (unless you're in a basement or bad coverage area?)
For ram, grab Semaphore manager from the market and enable Bigmem (requires reboot and breaks 720p recording). Also, whichever extra process you stopped that were up the roof, I would highly suggest unistalling if it's not something important, like a market app (no system process eh).
Click to expand...
Click to collapse
Bad coverage area. I'm in a small rural town where I work, but I live in a bigger city a little ways off, full bars all the time there lol. I actually had to flash a new modem when I got SlimBean, it's working great.
Well I ended up just killing everything not system apps to see what my RAM looked like and I got it down to 138mb. I also grabbed RAM booster off the market and it's keeping me around 100mb of free space.
I'll go grab the stuff you mentioned now and see what that does.
Thanks for the help. :3
Sent from my Samsung Captivate via Tapatalk 2.

athdaraxen said:
Bad coverage area. I'm in a small rural town where I work, but I live in a bigger city a little ways off, full bars all the time there lol. I actually had to flash a new modem when I got SlimBean, it's working great.
Well I ended up just killing everything not system apps to see what my RAM looked like and I got it down to 138mb. I also grabbed RAM booster off the market and it's keeping me around 100mb of free space.
I'll go grab the stuff you mentioned now and see what that does.
Thanks for the help. :3
Sent from my Samsung Captivate via Tapatalk 2.
Click to expand...
Click to collapse
I would uninstall RAM booster if I were you, it's a auto-kill app, which will drain your battery from killing apps that keep restarting and on top of that, it uses 39mb of ram itself!? That's insane. Just get Semaphore manager, it's made to work with your kernel and if you feel like you need the extra ram, enable Bigmem in the app's settings.

BWolf56 said:
I would uninstall RAM booster if I were you, it's a auto-kill app, which will drain your battery from killing apps that keep restarting and on top of that, it uses 39mb of ram itself!? That's insane. Just get Semaphore manager, it's made to work with your kernel and if you feel like you need the extra ram, enable Bigmem in the app's settings.
Click to expand...
Click to collapse
I figured it be a battery drain. These things usually are. I don't know if this makes any difference but I do have ROM Toolbox Pro. I know it has App Manager in it, I'll poke at it and see what it can do.
I did enable Bigmem, worked great! :3
The 720p thing, that's for video recording right?
Sent from my Samsung Captivate via Tapatalk 2.

athdaraxen said:
I figured it be a battery drain. These things usually are. I don't know if this makes any difference but I do have ROM Toolbox Pro. I know it has App Manager in it, I'll poke at it and see what it can do.
I did enable Bigmem, worked great! :3
The 720p thing, that's for video recording right?
Sent from my Samsung Captivate via Tapatalk 2.
Click to expand...
Click to collapse
I haven't looked much into ROM Toolbox Pro but I'm sure you'll be just fine with Bigmem as long as you keep track of your processes.
And yes, it breaks 720p video recording. Can be disabled though if you wanna use it.

Bigmem is definitely doing the trick. I've stayed around 100mb of free RAM since I activated it.
And that's actually fine with me, I have never recorded a video anyways so it won't even make a difference to me. Awesome.
I'm so glad it wasn't SOD thanks again for all the help.
Sent from my Samsung Captivate via Tapatalk 2.

A New member of the family and i have some questions

im using my z1 for 2 days and im impressed by its stunning performance , i updated to latest firmware once i booted my z1 . im not a new user of android but i have some questions .
1- why iam feeling that the flaps one day will broke down ?? and if so what will happen ? can i fix it ?
2- can i use sony z magnetic dock or it is necessary to bought z1 dock ?
3- sometimes i hear noise from speaker when im listening to music or playing a video
4- in camera app when i click on camera modes and click on + apps to open sony select it always gives me " no network connection . please try again later "
5- is there any way to disable mobile data annoying pop up that said it will charge you bla bla bla
6- in developer options i enabled dont keep activities so is there any threats or damage would happens ? or is t ok ? and is it useful for battery ?
7- now lets talk about problems .. im not satisfied with camera performance is there any guide to improve it ?
8 - Battery is my biggest problem !! it drains so damn fast .. i enabled stamina mode and low battery mode although i need an explanation for them ,, i installed battery guru and now in learning mode . i can tell that the percent decreased by 1% in less than 2 min i dont know what is happening
9 - why i cant root my device on latest frw ?? im in a bad need for rooting and i dont want to lose my apps and data
and thx in advance

also i forgot , im facing heating problem specially when im using he device while it is charging !!

Mohaakotb said:
why i cant root my device on latest frw ?? im in a bad need for rooting and i dont want to lose my apps and datae
Click to expand...
Click to collapse
You can downgrade just fine without losing data! If you're on newest, just downgrade to .352 (untick APPSLOG, CACHE, DATA) (http://forum.xda-developers.com/show....php?t=2469191)
Root with Vroot and then installed Dualrecovery (https://mega.co.nz/#!zNBjCLgK!RloqhT...TL-eSonTz4VBX4)
Flash (in Recovery) pre-rooted 257 fw (http://forum.xda-developers.com/show....php?t=2440408) + BusyBox/SU (http://d-h.st/M10)
Flash (in Flashtool) kernel/baseband from 257 stock tft (ticking everything except kernel/baseband) (http://forum.xda-developers.com/show....php?t=2469191)
Restart phone and reinstalled recovery.
You don't need to wipe any data when downgrading, upgrading. I didn't and it works just fine. Not saying it can't cause problems though.
adityakakat said:
which is better experia z1 or note 3
Click to expand...
Click to collapse
:silly:
Note 3 sucks .

thx for ur reply but why we cant root on latest frw ? is it a matter of time and they will make vroot work on it if so i will wait
i tried kingo and mobile entered in boot loop for 5 times then kingo said cantroot

thx for ur reply but why we cant root on latest frw ? is it a matter of time and they will make vroot work on it if so i will wait
i tried kingo and mobile entered in boot loop for 5 times then kingo said cantroot

Mohaakotb said:
thx for ur reply but why we cant root on latest frw ? is it a matter of time and they will make vroot work on it if so i will wait
i tried kingo and mobile entered in boot loop for 5 times then kingo said cantroot
Click to expand...
Click to collapse
I guess they haven't found a exploit yet. I see no reason to wait because you may need to wait a long time.

im afraid of doing any thing wrong i just bought the mobile .

Mohaakotb said:
im afraid of doing any thing wrong i just bought the mobile .
Click to expand...
Click to collapse
There's not really anything that can go wrong seeing as you can easily restore it.
I rooted my Z1 and Z Ultra within 5 minutes. And then I have never owned a sony device before.
You will be fine!

Ok I giva a try tommorw
Sent from my Z1 using xda app-developers app

Mohaakotb said:
im using my z1 for 2 days and im impressed by its stunning performance , i updated to latest firmware once i booted my z1 . im not a new user of android but i have some questions .......
and thx in advance
Click to expand...
Click to collapse
There's almost everything already answered on XDA threads, so try to check, you'll find many useful things.
And yeah...you will not broke flaps, believe me.
I have Xperia S over a year and flaps are still fine
They are very, very good and hard...
BTW - I would recommend you to buy a USB cable with a magnetic connector to easily charge your device.
It's easier than open flaps every single night
Also, you can easily root 257 - you just have to check XDA Z1 threads and you'll see hiw it's easy...
Sent from my Z1

how i root on 275 easily !! i searched alot

and what about other questions ??

This may sound stupid but I'm looking at potentially getting the Z1. How do you use the usb cables with magnetic connectors to charge your phone? Excuse my ignorance I've never heard of anything like that until now....
Sent from my EVO using xda app-developers app

On the left side of the Z1 there is a place to put a dock or to connect with magnetic cable instead of the normal charging area as it so easy than to open flap and connect with regular one
Sent from my C6903 using xda app-developers app

Mohaakotb said:
On the left side of the Z1 there is a place to put a dock or to connect with magnetic cable instead of the normal charging area as it so easy than to open flap and connect with regular one
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
You asked for an easy way to root. It's already easy, it's 4 clear steps .

1. Dunno, perhaps you're a bit insecure? They still work fine here, although I read some reports of people where they pop out too easily after a while.
2. As far as I know the dock dimensions differ just enough so that you are NOT able to use the Z dock.
3. Haven't noticed this
4. No such issue here, it this both on wifi as on data connection?
5. As far as I know it only tells you these kinds of things the first time and then you get an option right away to NOT display this again.
6. I'd say it would slow things down... A phone has memory for a reason, quick access. IOf it's in the background it shouldn't be using excessive battery anyway and if everything has to be started from scratch it could easily even take up more battery. Why disable it if you have no clear idea of the effect?
7. Manual 4:3, 8MP... Play around with the settings (mainly white balance and EV in the 'hard csaes'). Auto mode increases ISO too easily.
8. Install better battery stats, also... Check which processes take up the battery (the info you gave us tells us nothing). Do you have GPS and things like that always on? Bluetooth? Etc?
9. There simply is no root yet for the latest firmware, why? Dunno, apparently the standard ways do not work and ppl have not yet found a new way. Wait if yiou want, but it might take a while. Downgrouding, roioting and then updating is the only way for now.SweFox explained the process above (just replace the php?t=xxxxxx parts from the url with the ones in his links).
But you seem to be pushing buttons and changing settings you have no clue of, that's not making things better. Try one and see what effect it has, eliminate casues that way,

dagrim1 said:
1. Dunno, perhaps you're a bit insecure? They still work fine here, although I read some reports of people where they pop out too easily after a while.
2. As far as I know the dock dimensions differ just enough so that you are NOT able to use the Z dock.
3. Haven't noticed this
4. No such issue here, it this both on wifi as on data connection?
5. As far as I know it only tells you these kinds of things the first time and then you get an option right away to NOT display this again.
6. I'd say it would slow things down... A phone has memory for a reason, quick access. IOf it's in the background it shouldn't be using excessive battery anyway and if everything has to be started from scratch it could easily even take up more battery. Why disable it if you have no clear idea of the effect?
7. Manual 4:3, 8MP... Play around with the settings (mainly white balance and EV in the 'hard csaes'). Auto mode increases ISO too easily.
8. Install better battery stats, also... Check which processes take up the battery (the info you gave us tells us nothing). Do you have GPS and things like that always on? Bluetooth? Etc?
9. There simply is no root yet for the latest firmware, why? Dunno, apparently the standard ways do not work and ppl have not yet found a new way. Wait if yiou want, but it might take a while. Downgrouding, roioting and then updating is the only way for now.SweFox explained the process above (just replace the php?t=xxxxxx parts from the url with the ones in his links).
But you seem to be pushing buttons and changing settings you have no clue of, that's not making things better. Try one and see what effect it has, eliminate casues that way,
Click to expand...
Click to collapse
thx alot man your effort is appreciated .
1- lets hope that it will stick to its position
2-okay
3- okay
4- on data connection i didnt try on wifi may be it will work]
5- no it always give me this annoyning pop up
6-i disabled it
7- i dont know i thought that automatic mode will fit my usage but apparently it didnt . so in your opinion 8mp in manual mode is better than 20 ? so why they made it 20 mp !!
8-what is better battery status ? really battery issue is a pain in the ass !! im posting these pic to show how it works
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
9- i will give it a try

For battery problems checkout Greenify (you need to be rooted) app. Sometimes apps like facebook take your battery life while staying in the background that can cause potential wakelocks. Greenify will force those types of apps to shut off. I dont own Z1 but this app increased my battery life by %30-40 for sure.

i will give it a try once i root my mobile . but honestly im very sad with battery performance as it is my 4th day and it drains so fast so what about after one or 2 monthes when my z1 will be filled with apps and games !!

What is your screen brightness set to?

[Q&A] [ROM][AOSP] Google Edition S4/ Pure Nexus[SAFESTRAP] Feb 24th, 2015

Q&A for [ROM][AOSP] Google Edition S4/ Pure Nexus[SAFESTRAP] Feb 24th, 2015
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][AOSP] Google Edition S4/ Pure Nexus[SAFESTRAP] Feb 24th, 2015. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Just flashed this without having any trouble during the process until I powered off afterwards - or, attempted to. It hung on the power off screen, so I had to hold down the power button in order to turn it off. After I booted up again, Google Play Store crashed. I managed to get it to work long enough to install a few other apps (Textra, Lookout, Themer, and Dashclock) by disabling the Play Store app and then opening it. Whenever I tried to open these apps, they crashed upon opening and the app icon changed to the Android bot icon instead of the app's normal icon and the package name instead of the app name. After the first downloaded app crashed, then I got an error that Google Play Store crashed, and its icon changed the same way. I then attempted a factory reset within the ROM, but it hung on the power off screen. I held the power button again, booted back up, and it looks like all the preinstalled apps work except Play Store. When I try to test SuperSU, it says that Play Store has stopped and does not load a list of apps. Now, Google Now is saying that I "need Google Play Services, which is not supported by your device." Any idea what went wrong?

Had a similar problem, my mistake was not to follow the procedure EXACTLY as stated. It turns out that I did not wiped everything except from what's in the sd card, did that and boom! A nice ROM to play with. Give it a try.

I might give it a try again, but I know for a fact that I performed the wipe correctly.

Please, do tell how it went.

Worked this time! Thanks for your help!

Works great but have quite poor battery life, refuses to go into deep sleep.
msm-hsic-host wakelock, horrible wakelock pins the cpu 384 mhz min.
bugs ive found-
using the cast screen button renders a blank screen to my chrome cast.

Yup, battery life is pretty crappy. But had a similar battery life with stock NE3 firmware. In a couple of weeks I'll be getting a new battery. Bought my phone from eBay and it came with a used one, I'm just guessing at the moment.

I lost 30% overnight but this morning changed some wifi settings and loaded up betterbatterystats to see what's causing the wakelocks. Maybe it's something straightforward. I like the aosp a lot and going to try and make this rom work as a daily driver.
I'll post any findings or improvements.

ChristopherXDA said:
I lost 30% overnight but this morning changed some wifi settings and loaded up betterbatterystats to see what's causing the wakelocks. Maybe it's something straightforward. I like the aosp a lot and going to try and make this rom work as a daily driver.
I'll post any findings or improvements.
Click to expand...
Click to collapse
If possible go to the "raw info" in bbs, and check out your kernel wake locks, as far as the software went on this rom I saw no serious wakelocks, but when I switched to kernel view that's where the problem was. I lost all 80% over a period of ten hours while sleeping the other day. Thats with nothing installed but what came with the rom.

bestestever said:
If possible go to the "raw info" in bbs, and check out your kernel wake locks, as far as the software went on this rom I saw no serious wakelocks, but when I switched to kernel view that's where the problem was. I lost all 80% over a period of ten hours while sleeping the other day. Thats with nothing installed but what came with the rom.
Click to expand...
Click to collapse
Yep, same here. Phone never enters deep sleep. After about 3 hours lost 10% of battery. 80% of the partial wakelocks were msm_hsic_host wakes.

I think the issue has to do with the wifi. Even though wifi is set to be off when the screen's off, betterbatterystats shows the wifi is on 100% of the time. This makes some sense since there appears to be an issue with the wifi driver where after a full reboot my wifi won't work until I do a hotboot. This happens for everyone else right?
I will try and look into the wifi fix that was part of the masterpatch and see if that provides any fixes.

Google edition pure nexus safestrap i537
tHANKS HOPE IT WORKS
---------- Post added at 08:06 AM ---------- Previous post was at 07:50 AM ----------
Unable to mount system original? that is the last message I get before last reboot. please help.

Littile things
Speaker phone NOT working.. (I can hear the caller, but they cant hear me)
Cant get Tethering to work either. It activates but cant find it as a hot-spot/AP on my devices.
Do get ghosts vibes every once in a while.

S4 Active Speaker Phone Fix
rockinwaggy said:
The issue with speakerphone, for me, is that the other end of the call doesn't hear anything when using speakerphone. Turn speakerphone off and it's back to normal.
Click to expand...
Click to collapse
ChristopherXDA said:
Is your speaker phone working on calls?
Click to expand...
Click to collapse
McJeg said:
Speaker phone NOT working.. (I can hear the caller, but they cant hear me)
Cant get Tethering to work either. It activates but cant find it as a hot-spot/AP on my devices.
Do get ghosts vibes every once in a while.
Click to expand...
Click to collapse
This is a known issue on the S4 Active as discussed here: http://forum.xda-developers.com/showthread.php?t=2412645
Flashing the file labeled "S4 Active Speaker Phone Fix" aka "S4_Active_Call_Record_Fix.zip" fixed this issue for me.
ChristopherXDA, it appears you were involved in the original fix!
Joe-Tech, you may want to incorporate the zip's changes to the sound configs in /system/etc/snd_soc_msm into your next S4 Active build.

Ha, oh man thats a little embarassing. You're right, that fix works on this Rom too.
I tried some of the other fixes though like for Wi-Fi in the masterpatch and that doesn't work on this rom.

k3u::straylight said:
This is a known issue on the S4 Active as discussed here: <url>
Flashing the file labeled "S4 Active Speaker Phone Fix" aka "S4_Active_Call_Record_Fix.zip" fixed this issue for me.
ChristopherXDA, it appears you were involved in the original fix!
Joe-Tech, you may want to incorporate the zip's changes to the sound configs in /system/etc/snd_soc_msm into your next S4 Active build.
Click to expand...
Click to collapse
Thank you so much, this issue was bothering me because I kept forgetting and putting people on speaker lol. Fix worked perfectly, I can confirm

Love this ROM, battery life is poop, but, can bear with it. Here is my antutu score.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I see little feedback for this ROM. What can I do to give give more accurate and useful info?

fuel426 said:
I see little feedback for this ROM. What can I do to give give more accurate and useful info?
Click to expand...
Click to collapse
The rom is generally problem free. Aside from the battery life, it's quite solid. Both of his nexus style roms have this msm_hsic_host wakelock problem (I've tested the GE S4 rom). He is aware of this issue. Unfortunately, he has had some personal things happen lately, so he's not available to work on the rom. Family comes first.
Also, I recently test DS Battery Saver from the Play Store. Even on its most aggressive battery saving mode, deep sleep was never entered. So, don't bother.

Note 4 MM First Impressions and Bugs

Hi all,
Like any Note 4 owners I was waiting eagerly for the long awaited update of MM. However I have observed few possible bugs not encountered in previous versions :
1. S health can't sync of stored data due to unknown reasons.
2. Homesync, I have tried all possible ways to connect my phone to Samsung homesync but with no success. I had no such issues even when my phone was rooted.
3. Google fit, had a strange behaviour when entering activities manually I couldn't find point (.) while entering numbers.
4. Weather widget the transparent one couldn't update it says network failure but I have tried the other one and then it was fixed.
Did you observed any please share.
Sent from my SM-N910C using XDA-Developers mobile app

N190C:
1. Choppy bluetooth playback when screen is off. Cable headphones seem to play normal so far.
2. Still not fixed weather app (broken animation)
3. UI freezes when there is too much apps open. New apps do not open then, I'm not able to go back to internet browser or music app or any other app - white background/unresponsive screen. The only way is to close them all.
4. Choppy screen unlock, phone almost not responsive sometimes - however usually the UI works smoothly.
Quite serious issues if you ask me. I've cleared the cache but it didn't help.
I've made OTA, and I'm currently not going to reset phone because I'll loose way too much time to reconfigure it including business environment in the KNOX :|

My only issue after the update is that my phone turns off at 4% battery, but I think that was more of a battery problem and calibration might help, other than that no issues at all.
I used bluetooth earphone and no issues even on screen off/on.
Screen lock works smoothly as well as UI.
Wifi works as it should be and my data is much more faster than before.
Screen responsiveness is the first improvement I noticed.
I did factory reset after upgrading. (Been doing this everytime there is a major update.)
Additional:
Rooted and I've deleted some of unnecessary apps.
Sent from my SM-N910C using Tapatalk

I didn't experience any issue after the update, neither the issues above nor anything else.

screen off memo is not working at me. I am using the good lock app from samsung.
i dont know why it is not working

Luffy71 said:
screen off memo is not working at me. I am using the good lock app from samsung.
i dont know why it is not working
Click to expand...
Click to collapse
Try checking your settings...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N910C using Tapatalk

Finger print registered successfully but
When i lo locked the device to try it system ui problem and i restarted device
When it opened it directed me to the ** insert your password.. issues with fingerprint**

after activation of power saving mode gray line appeared in the top home screen how to remove?

I'm stuck with COJ5 5.1.1 locked bootloader here. After I upgrade to 6.0.1 will I be able to downgrade to something lower than COJ5 5.1.1 again..? My final objective is go back to KitKat here and run obscure old Android APPs...

umrafael said:
I'm stuck with COJ5 5.1.1 locked bootloader here. After I upgrade to 6.0.1 will I be able to downgrade to something lower than COJ5 5.1.1 again..? My final objective is go back to KitKat here and run obscure old Android APPs...
Click to expand...
Click to collapse
6.0.1 also has locked bootloader. i tried to downgrade to KK but failed

ahmd gomaa said:
Finger print registered successfully but
When i lo locked the device to try it system ui problem and i restarted device
When it opened it directed me to the ** insert your password.. issues with fingerprint**
Click to expand...
Click to collapse
I'm still on Lollipop and get this error from time to time.... annoying, but not relayed to MM.
Sent from my SM-N910U using Tapatalk

Guys, have you tried factory resetting before or after installing MM? Do the bugs still persist after that?
Cuz android tends to have weird bugs without factory resetting. I remember Lollipop f***ed up my previous device because of that.

Installed marshmallow Poland
didn't perform a factory reset
Every thing fine speed
Excerpt for the fingerprint issue
Will do clear fingerprint data and report back
Edit !!
After clearing fingerprint data same issue happened
And i found that the cause is the*good lock app**
After the phone restarted it removes the app and fingerprint works just fine
Sent from my SM-N910C using Tapatalk

Game tuner does not work. Cant install gameservice. Samsung app and they didnt update it
Sent from my SM-N910C using XDA-Developers mobile app

I believe some of the issues here is due to not doing hard reset. I always update trough odin and hard reset before and after install firmware

the thing i liked the most is the app opening animation (on nova/google now launcher),wasn't expecting much from this update but everything seems good so far.Screen-off notes and the new s-pen menu are welcome changes(and nice ones). Couldn't expect samsung to implement themes so dont even bother with that

I had erobot rom v.16 with xposed and suemax kernel 1.7.8 installed.
I made a backup using twrp, copied it to my pc and then installed the poland official MM build.
Install went smooth, no issues. After rebooting the phone and starting it up there were no issues on first glance (no factory reset) After that though while i was testing the phone apps started force closing, finger scanner wasnt working, lockscreen effects were laggy, keyboard opened slowly , etc. After a factory reset and a clean install and another factory reset after that , all the issues and bugs are gone for now. Even my battery life is good enough for my needs - i have both facebook and messenger + viber and instagram installed, and we all know those are battery eaters. So far so good, the most noticeable difference for me is the speed in the ui. I feel it being smoother and faster.

Question to guys who they updated to MM
update to MM or keep with Lollipop ???!!! & Why ???!!!

After installing MM Poland I've lost my root. How can I get it back? I need Viper4Android and some Tasker plugins working back P.S> I did full backup under TWRP. Please help. BTW: The overall performance is suprising!

I'm noticing a random fail with S Cover after the 6.0.1 OTA. Sometimes, when I close the S Cover, the screen remains on and the unique way to shut down the screen is pressing the power button.
When this error arrives, the unique way to fix it is to reboot the phone... and wait the next error appearance.
Anyone of you guys are noticing the same problem?