Related
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.
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
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...
since i clean installed 4.2.2 google factory image my launcher lag, so is apex launcher.
resolved after reboot but after a while it start to lag again.
there are some complainse with the same issue on paranoidandroid rom thread after updating to 4.2.2
http://forum.xda-developers.com/showpost.php?p=38140050&postcount=27902
yizhaq79 said:
since i clean installed 4.2.2 google factory image my launcher lag, so is apex launcher.
resolved after reboot but after a while it start to lag again.
there are some complainse with the same issue on paranoidandroid rom thread after updating to 4.2.2
http://forum.xda-developers.com/showpost.php?p=38140050&postcount=27902
Click to expand...
Click to collapse
try changing your kernel. AK works for me
yizhaq79 said:
since i clean installed 4.2.2 google factory image my launcher lag, so is apex launcher.
resolved after reboot but after a while it start to lag again.
there are some complainse with the same issue on paranoidandroid rom thread after updating to 4.2.2
http://forum.xda-developers.com/showpost.php?p=38140050&postcount=27902
Click to expand...
Click to collapse
I'm having the same issue. Its smooth after a reeboot but acts up soon after. Its really bugging me. Could anyone Please suggest things I could do, keeping everything stock.
Thanks.
sl4y3r88 said:
I'm having the same issue. Its smooth after a reeboot but acts up soon after. Its really bugging me. Could anyone Please suggest things I could do, keeping everything stock.
Thanks.
Click to expand...
Click to collapse
well, its seems like almost no one effected by this bug
so im trying to understand this.
im using the galaxy nexus car dock with 3 pins , r u?
yizhaq79 said:
well, its seems like almost no one effected by this bug
so im trying to understand this.
im using the galaxy nexus car dock with 3 pins , r u?
Click to expand...
Click to collapse
Having the same problem.
Factory reset and changing launcher to apex didn't work.
I'm not using the car connector
My nexus 7 is smooth though.
I'm gonna try getting back to 4.2.1
mathijs727 said:
Having the same problem.
Factory reset and changing launcher to apex didn't work.
I'm not using the car connector
My nexus 7 is smooth though.
I'm gonna try getting back to 4.2.1
Click to expand...
Click to collapse
i have no problems with my nexus 4...
back to 4.2.1
yizhaq79 said:
well, its seems like almost no one effected by this bug
so im trying to understand this.
im using the galaxy nexus car dock with 3 pins , r u?
Click to expand...
Click to collapse
No , im not using any car dock.
sl4y3r88 said:
No , im not using any car dock.
Click to expand...
Click to collapse
ok, so i downloaded the yakju ver 4.1.2 factory image and flashed it, reboot, then flashed the yakju 4.2.2.
did not uses the google account (no music, contacts, gmail, pictures, my life)
running 10 hours, no lag. will repor in 10 hours again, then sync with google account
hope ill find the solution, cous it looks like we the only 4 people on the planet that has this bug
i have this annoying lag too. Reboot solves it for a while but it will start lagging again. Changing to ak kernel doesnt work.
My N7 installed the upgrade acouple of days ago, lagged like hell until I cleared all cache then it was ok. But its back again. Trying to clear the cache again but the app is taking forever to load
I am afraid I've noticed that too two or three times. Only reboot resolves issue. It looks like a memory leak. I have never experienced that on stock 4.1.2 or 4.2.1.
Anyone found anything that could fix this?
Hello everybody, a few days back after installing stock odexed 4.2.2 I noticed some sort of stuttering when changing the desktops, I thought it was maybe a widget, the deepsleep battery saver app or a kernel problem buuuuut I did something, changed the wallpaper, the problem goes away, buttery smooth, unfortunately the problem comes back after a few hours.
:crying:
yizhaq79 said:
ok, so i downloaded the yakju ver 4.1.2 factory image and flashed it, reboot, then flashed the yakju 4.2.2.
did not uses the google account (no music, contacts, gmail, pictures, my life)
running 10 hours, no lag. will repor in 10 hours again, then sync with google account
hope ill find the solution, cous it looks like we the only 4 people on the planet that has this bug
Click to expand...
Click to collapse
Good night sleep and no lag... So next step is sync with Google account.
I'm downloading no apps, just sync the contacts and gallery.
No updating apps. I think its somthing to do with play store.
Someone suggested me to clear the cache of the stock launcher, that seemed to do the trick.
Sent from my Galaxy Nexus
lsv-1 said:
Someone suggested me to clear the cache of the stock launcher, that seemed to do the trick.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
For hour or two.
All of you guys noticing this lag is extremely odd, I'm on 4.2.2 stock and haven't noticed any lag whatsoever for a week that I've had it
Sent from my Galaxy Nexus using xda app-developers app
Sv: stock 4.2.2 launcher lag
So you haven't rebooted your device for one week at all?
Sent from my Galaxy Nexus using xda premium
yizhaq79 said:
For hour or two.
Click to expand...
Click to collapse
See the next post.
Sent from my Galaxy Nexus
I think that I found another possible solution, I just accessed the developer options and enabled the force gpu rendering, the lag came back, so, make sure these settings are unchecked
Sent from my Galaxy Nexus
I was looking at the N2 wiki on the cm website when I stumbled across a seemingly legitimate link for downloading an RC version of CM 10.1.2. Can anybody confirm that it is indeed version for our device and not some sort of weird joke??
Simply because last I heard was that the dev working on the cm official port was on hiatus and us SGN2 owners should expect our device to be abandoned. As the hard working devs would move onto devices who chipsets have much better makers supporting the ROM community. Yeah, I am a little bitter towards Samsung's apathy for the dev community
Anyway, if, IF, we finally have a (more-or-less) stable version of CM, it's time I leave Samsung's garish, badly designed house and move into AOSP swanky, high rise, beautiful looking apartment.
Not from these forums, but yeah, CM10.1 is entering RC stages before getting to the final CM10.1.3 stable build
CM10.1.2 should have a stable build for the GNII already though, although since I'm not from these forums I have no idea...
Sent from my GT-P7510 using Tapatalk HD
Oh very, very nice! Thankyou for confirming that. I'm still shocked that we are getting this version. I gave up ever expecting official cm in this capacity turning up on our device.
Any word if PIE controls re working??
Not a clue. I come from the Galaxy S forums, and as far as I recall PIE controls work fine on our builds. Don't see why they wouldn't on NII builds either.
Sent from my GT-P7510 using Tapatalk HD
I was just as shocked too, not to mention surprised! The S Pen works perfectly with pressure support, the ROM flies and it's overall much snappier than Samsung's TW based roms. I'd give it a go!
littlebigsnafu said:
I was looking at the N2 wiki on the cm website when I stumbled across a seemingly legitimate link for downloading an RC version of CM 10.1.2. Can anybody confirm that it is indeed version for our device and not some sort of weird joke??
Simply because last I heard was that the dev working on the cm official port was on hiatus and us SGN2 owners should expect our device to be abandoned. As the hard working devs would move onto devices who chipsets have much better makers supporting the ROM community. Yeah, I am a little bitter towards Samsung's apathy for the dev community
Anyway, if, IF, we finally have a (more-or-less) stable version of CM, it's time I leave Samsung's garish, badly designed house and move into AOSP swanky, high rise, beautiful looking apartment.
Click to expand...
Click to collapse
Wouldn't it have been quicker and easier to just check CM's official downloads for your answer?
http://get.cm/?device=n7100&type=RC
Using it n its awesome!!!
littlebigsnafu said:
Oh very, very nice! Thankyou for confirming that. I'm still shocked that we are getting this version. I gave up ever expecting official cm in this capacity turning up on our device.
Any word if PIE controls re working??
Click to expand...
Click to collapse
PIE is active only on full touch phones like nexus 4 as replacement for the virtual buttons!
We have phisical buttons so pie is disabled.
YES, me too think that the home button is too much stressed... because of this I save it at least for waking up the phone, using a paid app that uses the proximity sensor :victory:
It is effing awesome , albeit the NUMEROUS wakelocks.....
From google play services to google services to android os with bbs installed...
I did this http://forum.xda-developers.com/showthread.php?t=2357417 and installed DS battery.
It even play asphalt 8 better then Cleanrom... On cleanrom it was unplayable.
I would say this RC is damn good.
What about battery life though? I can barely get 15 hours on cm but I can easily get 1.5 days on clean rom ace.
Sent from my GT-N7105 using xda app-developers app
It really depends on screen on time. ... ^
New to all this but. . What would be a good asop replacement phone for the n2 ?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Good feedback so far, been researching UV to get better battery life once I make the switch. How's it been so far though on this CM version? hat's the average screen time on do you guy get? Any AOSP roms with near stock levels of battery??
Average screen time I get are 6 to 7 hours.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Google Services and Battery Solution
I flashed "cm-10.1.3-RC1-n7100.zip" only and every thing was OK for me.
But If I flashed Google Apps (GAPPS), the battery drain so quickly.
I tried both versions; "20130812" and "20130301".
From the battery menu in Android Setting, I find that "Google Services" uses most of the battery. I installed BetterBatteryStats and I find out that the device was awake even when screen was off and it cannot enter "Deep Sleep" mode.
I search and I come across these posts (1) and (2) and I tried to do the following:
1) I wiped cache and data.
2) flashed the ROM.
3) flash GAPPS. I used version 20130301 which has less Google Apps.
4) When Android started. I used "File Manager" to edit the following file "/system/bin/otablock". Add these lines to the end of the file:
Code:
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService\$Receiver
pm disable com.google.android.gsf/com.google.android.gsf.gtalkservice.ConnectionAuthErrorDialog
5) Reboot.
Now, the device enter Deep Sleep
binjubair said:
I flashed "cm-10.1.3-RC1-n7100.zip" only and every thing was OK for me.
But If I flashed Google Apps (GAPPS), the battery drain so quickly.
I tried both versions; "20130812" and "20130301".
From the battery menu in Android Setting, I find that "Google Services" uses most of the battery. I installed BetterBatteryStats and I find out that the device was awake even when screen was off and it cannot enter "Deep Sleep" mode.
I search and I come across these posts (1) and (2) and I tried to do the following:
1) I wiped cache and data.
2) flashed the ROM.
3) flash GAPPS. I used version 20130301 which has less Google Apps.
4) When Android started. I used "File Manager" to edit the following file "/system/bin/otablock". Add these lines to the end of the file:
Code:
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService\$Receiver
pm disable com.google.android.gsf/com.google.android.gsf.gtalkservice.ConnectionAuthErrorDialog
5) Reboot.
Now, the device enter Deep Sleep
Click to expand...
Click to collapse
You dont miss the official rom at all?
Sent from my GT-N7100 using xda app-developers app
binjubair said:
I flashed cm-10.1.3-RC1-n7100.zip only and every thing was OK for me.
Click to expand...
Click to collapse
Tempted to move back from 10.2 to this myself.
KeyzerSuze said:
New to all this but. . What would be a good asop replacement phone for the n2 ?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you can use PAC rom..wirh thor kernel or devil..i use thor kernel AOSP LSI version
binjubair said:
I flashed "cm-10.1.3-RC1-n7100.zip" only and every thing was OK for me.
But If I flashed Google Apps (GAPPS), the battery drain so quickly.
I tried both versions; "20130812" and "20130301".
From the battery menu in Android Setting, I find that "Google Services" uses most of the battery. I installed BetterBatteryStats and I find out that the device was awake even when screen was off and it cannot enter "Deep Sleep" mode.
I search and I come across these posts (1) and (2) and I tried to do the following:
1) I wiped cache and data.
2) flashed the ROM.
3) flash GAPPS. I used version 20130301 which has less Google Apps.
4) When Android started. I used "File Manager" to edit the following file "/system/bin/otablock". Add these lines to the end of the file:
Code:
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService\$Receiver
pm disable com.google.android.gsf/com.google.android.gsf.gtalkservice.ConnectionAuthErrorDialog
5) Reboot.
Now, the device enter Deep Sleep
Click to expand...
Click to collapse
Anyone else can check this?
Sent from my GT-N7100 using XDA Premium 4 mobile app