Related
Hi, I have an AT&T atrix running the CherryPi ROM with stock kernel and I have been overall very happy with it aside from two kinks.
1. Boot time is very long (over a minute and half) despite having bloatware frozen and startup apps cut to a minimum.
2. I can't receive MMS messages at all.Never mind.
I'm not all that concerned with MMS, but I've been considering installing Faux's kernel in hopes of a performance boost. I don't really want to overclock, though. I fixed this with some APN changing... Still ridiculous that I went months without MMS though.
Could my ROM be at the root of my problems?
If not, what kind of a performance gain would I be able to get with the optimized 1ghz kernel?
Would I have to wipe any data to install a different kernel? I answered this one myself.
Thanks.
Edit: I installed the kernel (wiped cache and dalvik cache) and further cleaned on bloatware, still taking over a minute to boot.
All this points me to a new/final question. Would CM7 yield a significant performance boost (say, boot times under 1 minute) without overclocking? It did absolutely. I installed CM7 and Faux's stopgap 1ghz kernel (which did say something about EXT4), my phone now boots in 20 seconds. That's over a minute of improvement from what I originally had. Topic can be closed/marked as solved.
Format your Rom to ext4 and it will increase speed
http://forum.xda-developers.com/showthread.php?t=1282691
Thanks for the information!
I'm downloading the fingerprint scanner enabled CM7 and doing a fresh install of everything. Would this script have any wonky side effects? I am a noob to android, but not to partitioning and filesystems. I've never seen a conversion go well that wasn't FAT16 to NTFS....
Edit: Installed CM7. It's so fast, it has so many features that I have been wanting. Wow is all I can say lol.
Id like to know what I can do about this on my stock gb only rooted atrix. I don't want to unlock my bootloader or use any custom roms. My startup time is about 4 1/2 to 5 minutes from time I press power button to time everything is loaded. I have not uninstalled any bloat but have frozen all social apps and authenticators and live wallpapers. Any ideas?
Sent from my MB860 using XDA App
In order to make it Ext 4 you have to have bootloader unloked and rooted.firat install the rom or if you already have its ok too.flash faux 123 kernels(any of them you want)
Go to cwm(it better to use RomRacers latest) and wipe cache and dalvik.
Do a nandroid backup for good measure.
Once this is done you install the ext4 script zip and that's it.
Reboot and check it out.if you get FCs then uninstall the apps that are force closing and go to cwm and fix permissions,then reinstall apps.
this makes your phone realky nice and fast,honestly I didn't have any apps force closing you have to follow the directions in the thread.
You will see your nandroid backup was ext3 and now you're ext4
If you decide later on to wipe dalvik or chache it might revert it back to ext3 if so just simply run the scrip zip again hope it helped
There is a root app called Autostarts that I think you will find useful.
WiredPirate said:
There is a root app called Autostarts that I think you will find useful.
Click to expand...
Click to collapse
Optimize Toolbox works great also. Just that in the latest version the language is not English anymore, (should get updated sometime to fix this). Lucky I remember what all the icons do and can use it blind! Finding an older version of this app in English will work.
The most current "lite" version is in English. It doesn't have the auto optimizer, but you can still manage autostart apps and log boot times.
(I'm thrilled, by the way, CM7 is booting in 19 seconds with all of my old apps restored. This is like having a brand new phone. We can mark this as solved on my part.)
WiredPirate said:
There is a root app called Autostarts that I think you will find useful.
Click to expand...
Click to collapse
Im cautious to pay for an app that im unsure of and never used. Wish I could try it first.
Sent from my MB860 using XDA App
pre4speed said:
Im cautious to pay for an app that im unsure of and never used. Wish I could try it first.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I can understand that for sure. It does do exactly what it says and works great on the Atrix. But like was pointed out above there are other apps that do the job and potentially w/o the price tag, I just haven't used them and so I can't speak on them. I would try to get the English version of the app that was mentioned and see if that works first (if it's a free app?..)
WiredPirate said:
I can understand that for sure. It does do exactly what it says and works great on the Atrix. But like was pointed out above there are other apps that do the job and potentially w/o the price tag, I just haven't used them and so I can't speak on them. I would try to get the English version of the app that was mentioned and see if that works first (if it's a free app?..)
Click to expand...
Click to collapse
I have Autostarts also, and it does in fact work as stated. I have just come to like Optimize Toolbox instead, and yes, it's free.
The biggest reason I never gave OT a try is cause there are 4 dif versions of it in the market and also because the cover art used to be not in English, and now that I know the app itself isn't in English either I'm even more turned off of it. However I know it is a popular app cause it was requested for the root apps list and I added it. I guess I'm just too ethnocentric to get past the whole developed in a dif language thing..
WHEN POSTING IN THIS THREAD:
DO NOT SPAM
ONLY POST QUESTIONS YOU HAVE REGARDING ISSUES YOU DO NOT SEE IN THIS FAQ
"Q" and "A" SOLUTIONS THAT SHOULD BE INCLUDED IN THIS THREAD
ISSUES WITH CURRENT SOLUTIONS IN THIS THREAD THAT DIDN'T SOLVE A PROBLEM
OR ANY QUESTIONS YOU HAVE REGARDING CM10.1 ITSELF! I HOPE TO FILL THIS THREAD UP WITH MANY MORE Q AND A SOLUTIONS TO HELP OTHER USERS AND DECREASE UNNECESSARY POSTS IN DEVELOPER SECTIONS! IF YOU CAN CONTRIBUTE: PLEASE FEEL FREE TO DO SO!
-------------------------------------------------------------------------------------------------------
Q: I flashed CM10.1 but my GPS won't lock. Is there a solution?
A: Absolutely!
(Optional) Use TitaniumBackup to backup your apps+data
Use Recovery to Backup your current state (System, Data, Boot)
Flash a Sense ROM of any kind (I use MeanBean)
(Don't forget to do your wipes, of course)
*Once booted into a Sense ROM*
Make sure your GPS is turned ON and open up Google Maps
Wait for your GPS to lock
Reboot into Recovery and Restore your Backup
(Don't forget to do your wipes, of course)
*Once booted back onto your CM10.1*
Make sure GPS is turned ON and open up Google Maps
Your GPS should now lock.
Q: I noticed screen tearing (glitch-like symptoms) on my CM10.1. Is there a solution?
A: Absolutely!
Go into Developer Options
Scroll down to "Disable HW Overlays"
Check the box to disable
Screen tearing is now gone.
NOTE! You will need to do this on each reboot!
Q: Developer Options don't exist on my CM10.1. Is it hidden?
A: Kind of.
Go into About
Scroll all the way down and tap the build 7 times
You will notice a message saying Developer Options was unlocked.
Q: How do I get the Play Store on my CM10X?
A: You'll need to download a compatible GApps (Google Apps
You can find the latest GApps in this thread
Q: Why isn't my WiFi connecting?
A: That issue is usually caused by your router. Simply reset or unplug your router for 15 seconds and try again.
Q: I installed an AOSP kernel and my phone has been rebooting. Why is that?
A: The kernel may not be supported with your current ROM.
Some kernels have a voltage script provided by the builder. Ask the developer if there is one available.
You can also download Kernel Tuner from the Play Store to change voltage.
Q: Voltage? Kernel Tuner? What now...?
A: Within' Kernel Tuner you will want to go into Voltage and use the "All +12.5 mV" which will up the Voltage in all areas. I found that having 192MHz at 900mV will make CM10.1 plenty stable while not affecting battery life significantly. ROM and Kernel may very. Do some Trial and Error to see what is suitable for you
Q: My internal storage says I have less than I really should. Did I ruin my internal SD Card?
A: No. Don't panic.
All you need to do is Wipe your Internal Storage.
Backup your files if you don't want to lose them, of course.
Problem should be solved.
Issue usually occurs when flashing from Sense to AOSP or flashing numerous ROM's in a short period of time.
Q: Where can I find the latest Deck Builds?
A: http://forum.xda-developers.com/showthread.php?t=2110920
You can also check the iRC channel (info in the thread above)
Also, search Google for "CM10 EVO LTE irc" and click the first link
Q: Should I flash Nightly Builds or Deck's Builds?
A: Nightly Builds are official CM builds which don't include all of Deck's maintenance, tweaks, etc... You'll find that Deck's Builds just happen to be more stable.
I feel like this was a waste of time. Lol.
Bump reserve.
CM 10.1 battery life
Delakit said:
I feel like this was a waste of time. Lol.
Bump reserve.
Click to expand...
Click to collapse
I've been using CM 10.1 ever since it first came out .I love it but the only problem i got is the terrible battery life I've been experiencing .It has gotten lot worst over time now my phone barely last a couple of hours per charge.Is there any advice you can give me to get better battery life?
ive done clean and dirty installs to find a solution but still get the same result and i've never use another kernel with the ROM. The best battery life i've experience with my phone was with stock rom when i used to get 24hrs on one charge .i'm seriously thinking about going back to stock but i love CM10.1
PLEASE HELP A BROTHA OUT
hakeem0996 said:
I've been using CM 10.1 ever since it first came out .I love it but the only problem i got is the terrible battery life I've been experiencing .It has gotten lot worst over time now my phone barely last a couple of hours per charge.Is there any advice you can give me to get better battery life?
ive done clean and dirty installs to find a solution but still get the same result and i've never use another kernel with the ROM. The best battery life i've experience with my phone was with stock rom when i used to get 24hrs on one charge .i'm seriously thinking about going back to stock but i love CM10.1
PLEASE HELP A BROTHA OUT
Click to expand...
Click to collapse
That is pretty weird. I had that problem on the EVO 3D before. Were you or are you using any custom kernel, kernel tuner, or scripts at all?
I know, too, that the battery does seem to drain a bit fast at first but then it gets more subtle. MeanBean has been draining me worse than CM10.1 right now.
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
Delakit said:
That is pretty weird. I had that problem on the EVO 3D before. Were you or are you using any custom kernel, kernel tuner, or scripts at all?
I know, too, that the battery does seem to drain a bit fast at first but then it gets more subtle. MeanBean has been draining me worse than CM10.1 right now.
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
Click to expand...
Click to collapse
Im not using anything extra,just the ROM as is . Also tried MeanBean got about 5 to 6 hours on one charge but still isnt anywhere close to 24 hrs on one charge with stock ROm
hakeem0996 said:
Im not using anything extra,just the ROM as is . Also tried MeanBean got about 5 to 6 hours on one charge but still isnt anywhere close to 24 hrs on one charge with stock ROm
Click to expand...
Click to collapse
MeanBean has never treated me well on battery life no matter what I do. Not on my replacement anyway. On my other LTEvo it was working great. But... CM10.1's battery life shouldn't be that bad. Could always use Kernel Tuner to manage the CPU and Gov. a bit. Trial and error until you find a satisfied combination. I generally use Ondemand as opposed the interactive. I noticed Ondemand gave me better battery life. Haven't done much with the CPU speeds in a while so I'm not going to be too much help there... I also use System Panel to monitor apps, system, memory, and use its built-in task killer.
Delakit said:
MeanBean has never treated me well on battery life no matter what I do. Not on my replacement anyway. On my other LTEvo it was working great. But... CM10.1's battery life shouldn't be that bad. Could always use Kernel Tuner to manage the CPU and Gov. a bit. Trial and error until you find a satisfied combination. I generally use Ondemand as opposed the interactive. I noticed Ondemand gave me better battery life. Haven't done much with the CPU speeds in a while so I'm not going to be too much help there... I also use System Panel to monitor apps, system, memory, and use its built-in task killer.
Click to expand...
Click to collapse
ill give it a try.thanks
How to disable shutter sound?
In older versions of CM there used to be an option in system settings to disable the shutter sound in the camera app. I can't seem to find any options either in the camera settings or in the system settings for this in CM10.1. Anyone know if this is there or not? Or is it coming in a future version?
---------- Post added at 03:58 PM ---------- Previous post was at 03:51 PM ----------
hakeem0996 said:
ill give it a try.thanks
Click to expand...
Click to collapse
I had some trouble with apps wakelocking (for lack of a better word) when I first installed CM10.1. You can identify some of those with the wakelock detector app.
https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector
Thanks for putting this post together. I have always used Sense but have been wanting to try a CM10.1 ROM. This information is very helpful.
A question that I have is what bugs or issues are currently associated with CM10.1? Most of the CM10.1 ROMs under Bug List say "Any bugs currently in latest CM10.1." Is there a centralized place that lists all of the issues? Thanks.
1TonyC said:
Thanks for putting this post together. I have always used Sense but have been wanting to try a CM10.1 ROM. This information is very helpful.
A question that I have is what bugs or issues are currently associated with CM10.1? Most of the CM10.1 ROMs under Bug List say "Any bugs currently in latest CM10.1." Is there a centralized place that lists all of the issues? Thanks.
Click to expand...
Click to collapse
The only thing I noticed going wrong was my background will occasionally disappear (go black). Sometimes it will pulsate or strobe. Only happens when I sleep the phone while in Messages, and wake the phone. After unlocking, the background will either be black, be black for a while and all of the sudden pop my background image back up, or just act normal. I have no customizations or anything so I'm not sure why this occurs. Otherwise, the Vertical orientation option for the App Drawer is still messy as it always has been. That's all I've noticed but I haven't tested the music player yet .
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
nebhead said:
In older versions of CM there used to be an option in system settings to disable the shutter sound in the camera app. I can't seem to find any options either in the camera settings or in the system settings for this in CM10.1. Anyone know if this is there or not? Or is it coming in a future version?
---------- Post added at 03:58 PM ---------- Previous post was at 03:51 PM ----------
I had some trouble with apps wakelocking (for lack of a better word) when I first installed CM10.1. You can identify some of those with the wakelock detector app.
https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector
Click to expand...
Click to collapse
Power Shutter? If so, that's in the Camera app settings. Click the bottom-right screen-button and choose the bottom-center settings screen-button. I also have apps that'll randomly open when I wake the phone but I figured that was just because of the phone being in my pocket, turning on, and going to the app. It will open to the clock.
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
Delakit said:
Power Shutter? If so, that's in the Camera app settings. Click the bottom-right screen-button and choose the bottom-center settings screen-button. I also have apps that'll randomly open when I wake the phone but I figured that was just because of the phone being in my pocket, turning on, and going to the app. It will open to the clock.
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
Click to expand...
Click to collapse
Actually, not referring to Power-Shutter. I'm referring to the actual sound that is made when you take a photo. It's a bit jarring/annoying to have it "dleep!" when I take photos. Back in CM7 I remember that we could turn that sound off.
Delakit said:
I feel like this was a waste of time. Lol.
Bump reserve.
Click to expand...
Click to collapse
Any source of info or attempt to help folks that either dont know or cant figure things out on their own is never a waste of time bro. Thanks
*Information IS the most dangerous weapon of all*
nebhead said:
Actually, not referring to Power-Shutter. I'm referring to the actual sound that is made when you take a photo. It's a bit jarring/annoying to have it "dleep!" when I take photos. Back in CM7 I remember that we could turn that sound off.
Click to expand...
Click to collapse
I looked everywhere and couldn't find an option. I really don't have the time to dig further into the actual coding either, unfortunately.
Delakit said:
I looked everywhere and couldn't find an option. I really don't have the time to dig further into the actual coding either, unfortunately.
Click to expand...
Click to collapse
Thanks for trying. If anyone else knows or has time to check it would be greatly appreciated.
only issue ive been getting since the 4/13 buld and as well as the 4/16 build is my phone fcs when someone calls. really annoying. especially since not even running a kernel only stock . and have done a few full wipes and clean installs. been diving me nuts
kaos420 said:
only issue ive been getting since the 4/13 buld and as well as the 4/16 build is my phone fcs when someone calls. really annoying. especially since not even running a kernel only stock . and have done a few full wipes and clean installs. been diving me nuts
Click to expand...
Click to collapse
Odd. Never had that issue before. Bad download?
Sent from my EVO using xda app-developers app
When I flashed CM 10.1 the only thing that worked was power button and volume. The screen was unresponsive, my bootloader is unlocked and I'm s-off hboot 2.09
Sent from my EVO using xda premium
WOLF26915 said:
When I flashed CM 10.1 the only thing that worked was power button and volume. The screen was unresponsive, my bootloader is unlocked and I'm s-off hboot 2.09
Sent from my EVO using xda premium
Click to expand...
Click to collapse
And as you'll find stated numerous times: the latest touchpanel firmware isn't yet supported with most, if not all, AOSP ROM's. S-OFF, which will make you downgrade, and you'll be able to use your AOSP ROM's. And then you can update to the latest firmware minus the tp update.
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
https://play.google.com/store/apps/details?id=com.tushar.cmspen2
This is an application which allows detection of the S Pen detachment even on AOSP/AOKP/CM based ROMs.
It has only been tested on the Note 2 by me. If it works on your note device please let me know so that I can add it to the list of compatible note devices.
Explanation of how it works:
The android system automatically adds event files for each input device it detects when being installed. These event files are located in /dev/input/eventX where X denotes a particular device. These event files can be read using native C code for which I use an API provided by Radu Motisan which can be found here and also a bit more information about the event files can be found there. So now using this interface I find the event file for the S Pen and then continously read it to see if the value of the S Pen sensor has been changed. Whenever it changes I broadcast the corresponding Intent which was broadcasted by Samsung so that any applications which work based on that Intent can work even on these ROMs without having to change any of their code.
An interesting thing is that this feature is already present in CyanogenMod i.e S-Pen Power saving mode which disables the s pen touch decoder when the s pen is inserted. I fail to understand why they are not doing the same thing that I am doing through my application and save all of us the trouble.
Phone vibrates when i inserted/detached s-pen, so it works? I have note2 lte (n7105) with latest rootbox nightly.
Sent from my GT-N7105 using Tapatalk 4 Beta
tushar9989 said:
https://www.dropbox.com/s/eebkzugsm7ek12s/CM S-Pen Addon.apk
Guys this is the beta version of my application which can detect S Pen detection even on CyanogenMod(works for me on JellyBeer Rom).
Please test it out and tell me if it works on your ROM, it mimics the Intent which is broadcast-ed by Samsung when the S Pen is inserted/detached so any applications which use that intent should work fine.
You can use it in conjunction with my application S Pen Helper to mimic page-buddy on CM 10. Here is the playstore link https://play.google.com/store/apps/details?id=com.tushar.spen_helper
Click to expand...
Click to collapse
It works well, also Using jellybeer rom. Very good, one thing, how to auto launch a note app? There is the option to launch something, but can't choose what to launch, unless I'm blind.(which could easily be the case)
jnr21 said:
Phone vibrates when i inserted/detached s-pen, so it works? I have note2 lte (n7105) with latest rootbox nightly.
Sent from my GT-N7105 using Tapatalk 4 Beta
Click to expand...
Click to collapse
If it's vibrating means it's working
bungknees said:
It works well, also Using jellybeer rom. Very good, one thing, how to auto launch a note app? There is the option to launch something, but can't choose what to launch, unless I'm blind.(which could easily be the case)
Click to expand...
Click to collapse
I had made spen-helper keeping Samsung based ROMs in mind so it selects s note by default but since it's not there on cm10 so it's blank just click below the enable launch toggle will pop up a dialog to change it. I'll fix it in the next version. Also I suggest not to keep the event monitor running in the background as it drains the battery a lot. I'm looking for a method to fix the battery drain currently.
tushar9989 said:
If it's vibrating means it's working
I had made spen-helper keeping Samsung based ROMs in mind so it selects s note by default but since it's not there on cm10 so it's blank just click below the enable launch toggle will pop up a dialog to change it. I'll fix it in the next version. Also I suggest not to keep the event monitor running in the background as it drains the battery a lot. I'm looking for a method to fix the battery drain currently.
Click to expand...
Click to collapse
Ok, thanks for the tip. Great work
Edit: just looked at battery now, and holy crap, yes it does drain it. But good start.
Uploaded to play store and source code to GitHub and also a brief explanation on how it works
v0.2.1 out
-Bug fixes and optimizations
-Changed app version to reflect beta status
app lauch settings
tushar9989 said:
v0.2.1 out
-Bug fixes and optimizations
-Changed app version to reflect beta status
Click to expand...
Click to collapse
Can't see the "app launch settings" you've mentioned. Did you remove it? The batery drain is visible but i think it's not catastrophic. I wonder why the CM team never got around implementing this because they already have the building blocks...
leonard.pitzu said:
Can't see the "app launch settings" you've mentioned. Did you remove it? The batery drain is visible but i think it's not catastrophic. I wonder why the CM team never got around implementing this because they already have the building blocks...
Click to expand...
Click to collapse
The app launch settings are not there in this application. If you want those features you will have to use this application in conjunction with this.
Regarding the battery drain I fixed it in the last version if you are still having battery drain I would suggest increasing the polling value to 1000 which is responsive enough and not at all taxing on the battery
tushar9989 said:
The app launch settings are not there in this application. If you want those features you will have to use this application in conjunction with this.
Regarding the battery drain I fixed it in the last version if you are still having battery drain I would suggest increasing the polling value to 1000 which is responsive enough and not at all taxing on the battery
Click to expand...
Click to collapse
Thanks for the update. I already use the app you've pointed at - just thought your app could do the same (my bad...). On the battery side i disabled you app and the s pen helper leaving me with "stock" CM10.1 + a bunch of play store downloaded apps. The battery drain is still there so the good news is that your app works as expected - that is not causing any dramatic power consumption. The the bad side... the battery drain is caused by something else. I've installed wakelock doctor and am waiting to see which is the app causing the mentioned battery drain (~4%/hour - roughly 4 times more than usual).
Thanks for your quick support!
leonard.pitzu said:
Thanks for the update. I already use the app you've pointed at - just thought your app could do the same (my bad...). On the battery side i disabled you app and the s pen helper leaving me with "stock" CM10.1 + a bunch of play store downloaded apps. The battery drain is still there so the good news is that your app works as expected - that is not causing any dramatic power consumption. The the bad side... the battery drain is caused by something else. I've installed wakelock doctor and am waiting to see which is the app causing the mentioned battery drain (~4%/hour - roughly 4 times more than usual).
Thanks for your quick support!
Click to expand...
Click to collapse
The battery drain is a problem in most of the CM based ROMs. I use Sentinel ROM which gives much better battery life than any of the other ROMs I tried. Link is in my signature in case you want to try it out.
tushar9989 said:
The battery drain is a problem in most of the CM based ROMs. I use Sentinel ROM which gives much better battery life than any of the other ROMs I tried. Link is in my signature in case you want to try it out.
Click to expand...
Click to collapse
Thanks for pointing out that CM causes battery drain. I've previousely used CM on all my devices (HTC Desire, Nexus S, Galaxy Nexus, Note I & II and Nexus 7) and it turned out to being great. I'll test a bit more and then jump over to Sentinel ROM.
This is a great application...
Many thanks for this huge step forward !!
tushar9989 said:
The battery drain is a problem in most of the CM based ROMs. I use Sentinel ROM which gives much better battery life than any of the other ROMs I tried. Link is in my signature in case you want to try it out.
Click to expand...
Click to collapse
I'm using Notes 1, Google Play will not let me download it.
Could you remove the Google Play restrictions?
or maybe just attach the .APK file here in XDA?
Thanks
AllGamer said:
I'm using Notes 1, Google Play will not let me download it.
Could you remove the Google Play restrictions?
or maybe just attach the .APK file here in XDA?
Thanks
Click to expand...
Click to collapse
Sorry the Note 1 does not have the sensor for detecting the s pen
tushar9989 said:
Sorry the Note 1 does not have the sensor for detecting the s pen
Click to expand...
Click to collapse
Thanks for the heads up
Issue with the app working reliably on an ASOP ROM
tushar9989 said:
This is an application which allows detection of the S Pen detachment even on AOSP/AOKP/CM based ROMs.
It has only been tested on the Note 2 by me. If it works on your note device please let me know so that I can add it to the list of compatible note devices.
The source code can be found here
The android system automatically adds event files for each input device it detects when being installed. These event files are located in /dev/input/eventX where X denotes a particular device. These event files can be read using native C code for which I use an API provided by Radu Motisan which can be found and also a bit more information about the event files can be found there. So now using this interface I find the event file for the S Pen and then continously read it to see if the value of the S Pen sensor has been changed. Whenever it changes I broadcast the corresponding Intent which was broadcasted by Samsung so that any applications which work based on that Intent can work even on these ROMs without having to change any of their code.
An interesting thing is that this feature is already present in CyanogenMod i.e S-Pen Power saving mode which disables the s pen touch decoder when the s pen is inserted. I fail to understand why they are not doing the same thing that I am doing through my application and save all of us the trouble.
Click to expand...
Click to collapse
I want to thank you for your hard work on this application, and the level to which you've gone to enable s-pen support in non-touchwiz ROMs. I just made the jump to Carbon ROM (4.3) this weekend after using my Sprint Note 2 (SPH-L900) with rooted, stock 4.1 since I got it at launch last year. I am totally fed-up with touch-wiz and I am really amazed at the difference the ASOP ROM is making for me.
I installed your app and it seemed to work perfectly for about 20 mins or so, then the next time I pulled out my s-pen it didn't recognize the event. Rebooting didn't make a difference, the only thing that made it work again was uninstalling, and then reinstalling the app. I am really confused as to why it stops working. I've checked, and both background services are still active, not cached, and the main program shows as running in my application manager. Do you have any thoughts or suggestions?
I can't paste links into XDA as I don't contribute all that often, but if you want to check out more on Carbon ROM I read about it on galaxynote2root, listed under the recent posts. The ROM is extremely stable and I'm very baffled as to why it isn't cooperating with your app! Thanks!
bigjl99 said:
I want to thank you for your hard work on this application, and the level to which you've gone to enable s-pen support in non-touchwiz ROMs. I just made the jump to Carbon ROM (4.3) this weekend after using my Sprint Note 2 (SPH-L900) with rooted, stock 4.1 since I got it at launch last year. I am totally fed-up with touch-wiz and I am really amazed at the difference the ASOP ROM is making for me.
I installed your app and it seemed to work perfectly for about 20 mins or so, then the next time I pulled out my s-pen it didn't recognize the event. Rebooting didn't make a difference, the only thing that made it work again was uninstalling, and then reinstalling the app. I am really confused as to why it stops working. I've checked, and both background services are still active, not cached, and the main program shows as running in my application manager. Do you have any thoughts or suggestions?
I can't paste links into XDA as I don't contribute all that often, but if you want to check out more on Carbon ROM I read about it on galaxynote2root, listed under the recent posts. The ROM is extremely stable and I'm very baffled as to why it isn't cooperating with your app! Thanks!
Click to expand...
Click to collapse
I think that is happening because you have screen off detection disabled and you are locking the phone before re inserting the s pen. If that happens again you can try inserting the pen then enabling and disabling the detection from the application's settings.
Running unofficial cm11 4.4 Kit Kat and on ART. Any chance of support in the future?
Dwnhiller said:
Running unofficial cm11 4.4 Kit Kat and on ART. Any chance of support in the future?
Click to expand...
Click to collapse
Have you tried using it? Because some users said it works on CM 11.
I've heard that the ART in Z2 is still Open-Beta stage. So I need your few words about this stuff, desperately.
Apparently, most of my games are not compatible with ART. So what will happen if I change the runtime? Remains the status quo, slows them down or even ruins my game? Also, the same question for all Apps that does not know what ART is.
My device has been root for some time. How's that be affected by ART? Will any problems occur?
And, ART_Is it really THAT GOOD?
Silverylos said:
I've heard that the ART in Z2 is still Open-Beta stage. So I need your few words about this stuff, desperately.
Apparently, most of my games are not compatible with ART. So what will happen if I change the runtime? Remains the status quo, slows them down or even ruins my game? Also, the same question for all Apps that does not know what ART is.
My device has been root for some time. How's that be affected by ART? Will any problems occur?
And, ART_Is it really THAT GOOD?
Click to expand...
Click to collapse
The ART in android 4.4 kitkat is no where near ART in android L. The ART in 4.4 kitkat is in an early stage, but it should speed up app animations (just a tad) and battery life should be improved (still, just a tad). Apart from those nice changes, it also makes booting the phone take longer. If you almost never turn your phone off all the way or reboot it, that shouldn't matter. But ART in android L improves battery a LOT and speeds things up a good amount. As for apps that don't work with ART? I know there are lists you can find out there where people have tested lots of apps so they should be able to tell you basically which apps don't work. I'm using dalvik right now because I need Xposed Installer and BusyBox which both do not work with ART (as far as I know). Anyways, you can switch to ART, try it out, and if too many apps won't work, just switch back to dalvik. All of your apps should work if you switch back to dalvik. ART has no lingering effects if you switch back.
EDIT: Also, when I say an app won't work with ART, that means that the app simply won't work at all. It will simply crash and you'll go right back to the home screen. Any app that does work, should be the same as an app in dalvik but it might shave a couple milliseconds off from how long the app takes to launch. But it's basically an all or nothing as to whether the app will work or not with ART. It either doesn't work at ALL or it works the same/better.
Silverylos said:
And, ART_Is it really THAT GOOD?
Click to expand...
Click to collapse
It's not a question of wether or not it's good, from L, as i understand it, it will be the default runtime.
ghostofcain said:
It's not a question of wether or not it's good, from L, as i understand it, it will be the default runtime.
Click to expand...
Click to collapse
The Z2 doesn't have android L, or any L-based roms. I assume he was asking if the ART in kitkat was good.
Android 5.0 is far from finished and so is Art Runtime/Compiler
and it is surely worth the wait
Instead of apps being compiled every time you open the app that being how dalvik vm works. the apps are already compiled from when they were installed.
this lowers app opening time
lowers risk of bugs in apps during run time
generaly more free space in system partitions
frees up some ram but this is app dependant
- saves some battery
overal lower system load cpu mostly
faster booting times potentialy
no need to deodex to mod, simply clear your cache and app compile output cache
art runtime is certainly much better than dalvik
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
What is CyanogenMod ? It is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones.
Notes: CyanogenMod's stock kernel forces encryption. If you're unencrypted use a custom kernel to keep it.
Also this thread assumes you have kept up to date bootloader and radio !!!
The latest can be downloaded here Shamu Factory images around 1gb!. But i recommand you to flash through TWRP the Bootloader and Radio from here Radio and Bootloader around 60mb.
Installation is simple
1/Download rom + gapps (C-apps optional)
2/flash through recovery (Twrp or CM recovery)
3/Enjoy!!!
----->CyanogenMod Download<-----
----->Open GApps<-----
last--CM13--nightlylast--CM12.1--nightly
Changelog
CyanogenApps
Twrp
Sources: Kernel & Rom
XDA:DevDB Information
[ROM] CyanogenMod14.1 {Nightlies and Snapshots} & Cm13, ROM for the Nexus 6
Contributors
Dead-neM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Up to date firmware (Fastboot+Radio)
Version Information
Status: Nightly
Current Stable Version: Everymonth
Current Beta Version: Everyday
Created 2016-04-22
Last Updated 2016-11-21
Reserved
Q&A
hum yes post your problem here after some research and you'll be helped
...
Reserved
Do not declare a bug here in the idea that they'll be fixed. Here we discuss, share everything related to our CM N6
so this is where we post from now on?
wmfreak said:
so this is where we post from now on?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using Tapatalk
Yay! Best ROM IMHO.
Can i run this in F2FS partitions Lety me know Thank's in advance!!!
Sent from my shamu using XDA Labs
caballon said:
Can i run this in F2FS partitions Lety me know Thank's in advance!!!
Sent from my shamu using XDA Labs
Click to expand...
Click to collapse
Sure, CM13 has been compatible since at least the beginning of this year
Hi, Thank you all making CM work and supporting this device. I particularly love this phone since this is Motorola (well, sort of) with a AMOLED screen, but more importantly it's the CM's custom features that urged me chose this phone.
I have been using the 160402 nightly with no major problem, only having two live lock screen force closes after reboot. Yesterday I hoped to upgrade to a more recent nightly, but that turned out to fail. I got constant FC's on Phone app, although the LLS ones were gone.
I tried cleaning Phone app's data, disabling xposed, but no help. I don't want to wipe data or otherwise I have to TiBu and then manually set up a ton of things.
The new post OP gives me a hint maybe my radio is too old (MDM9625_104662.22.05.32R) so I'm now trying to flash the latest factory radio and flash the yesterday's nightly again. Also it may be true but not so obvious that my cell signal (Tmobile LTE) gets frequently dropped (no signal/emergency only). I didn't test long before TWRPing back to the old working nightly.
Just want to check out at now if there is any other thing I have missed? Or why am I getting constant Phone app FC?
Edit: I updated the radio to .34R but it didn't help. The Phone app crashes every time I launch it, without giving a report button and it even didn't give me a chance hit the OK button before it disappears. I managed to call somebody with the contacts app and I heard the dialing tone. I was able to hang up the call with the notification action button. Everything looks fine except for the "Dialer" app.
Has the Sprint LTE issue been fixed by CM yet? IIRC the issue is once the Nexus 6 (running CM13 of course) drops down to 3G, it will never go back to LTE.
@cyrildtm
Going to have to bite the bullet and clean flash then.
Lawlrus said:
@cyrildtm
Going to have to bite the bullet and clean flash then.
Click to expand...
Click to collapse
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Snap camera in this version yet?
cyrildtm said:
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Click to expand...
Click to collapse
Yeah, I mean I clean flash everything but I know everyone is different.
That's the nice thing about ROMs though, you don't HAVE to flash every nightly, I know I sure don't lol.
If they push a new commit I like then I update, but if everything is kosher, then the hell with it.
Yeah, is the sprint LTE issue fixed?
Sent from my Nexus 6 using XDA-Developers mobile app
cyrildtm said:
Hi, Thank you all making CM work and supporting this device. I particularly love this phone since this is Motorola (well, sort of) with a AMOLED screen, but more importantly it's the CM's custom features that urged me chose this phone.
I have been using the 160402 nightly with no major problem, only having two live lock screen force closes after reboot. Yesterday I hoped to upgrade to a more recent nightly, but that turned out to fail. I got constant FC's on Phone app, although the LLS ones were gone.
I tried cleaning Phone app's data, disabling xposed, but no help. I don't want to wipe data or otherwise I have to TiBu and then manually set up a ton of things.
The new post OP gives me a hint maybe my radio is too old (MDM9625_104662.22.05.32R) so I'm now trying to flash the latest factory radio and flash the yesterday's nightly again. Also it may be true but not so obvious that my cell signal (Tmobile LTE) gets frequently dropped (no signal/emergency only). I didn't test long before TWRPing back to the old working nightly.
Just want to check out at now if there is any other thing I have missed? Or why am I getting constant Phone app FC?
Edit: I updated the radio to .34R but it didn't help. The Phone app crashes every time I launch it, without giving a report button and it even didn't give me a chance hit the OK button before it disappears. I managed to call somebody with the contacts app and I heard the dialing tone. I was able to hang up the call with the notification action button. Everything looks fine except for the "Dialer" app.
Click to expand...
Click to collapse
Hi I'm not using the stock dialer app but the Google one from playstore and i don't have force close so that's not a radio problem but an app problem. In fact having radio up to date normally improve stability over network cell comprehension etc... That's not a big deal but it is better to have a Marshmallow fastboot + radio on a Cm13 build which is Marshmallow based
Cm13 nightly can be really messed up a day but not an other. i think you just catch the wrong one
cyrildtm said:
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Click to expand...
Click to collapse
Used titanium to restore data of system app have always been buggy for me on every phone tablet that i've possessed. TiBu is usefull for data app
Btw a clean flash doesn't mean to restore data of a previous rom lol
Lawlrus said:
That's the nice thing about ROMs though, you don't HAVE to flash every nightly, I know I sure don't lol.
If they push a new commit I like then I update, but if everything is kosher, then the hell with it.
Click to expand...
Click to collapse
I agree with you. Nightlies sometimes can be awesome but sometimes awful. I went to look at the github page for the dialer app and found they recently put quite a lot of commits so maybe one or two is breaking things but anyways those smart people will figure it out sooner or later. I will just wait and take another free software
I bumped up from a March nightly mainly because of a recent CVE patch (of course that went into the 0401 build mod). Other than that I don't really see any urgent reason for increasing the counters in my daily driver again.
Dead-neM said:
Hi I'm not using the stock dialer app but the Google one from playstore and i don't have force close so that's not a radio problem but an app problem. In fact having radio up to date normally improve stability over network cell comprehension etc... That's not a big deal but it is better to have a Marshmallow fastboot + radio on a Cm13 build which is Marshmallow based
Cm13 nightly can be really messed up a day but not an other. i think you just catch the wrong one
Click to expand...
Click to collapse
I'm now on MOB30D radio (34R shown in settings, didn't copy down the version number shown in bootloader, but it did increase after flashing) and I can always make a phone call even now with an older nightly. so I can confirm the radio is working. I also noticed after flashing and first boot, when CM is about to finish "optimizing apps" the system gets a hot reboot (restart from animation) - oh btw another long-time bug is i never get themed boot animation unless i make a hot reboot (by FCing or any other way). Anyone same here?
From what I can remember the Dialer app has been a failure to me for more than a week. They did make a NPE fix there but seemed no help. Maybe I should install the Google's dialer as you do. I can still remember the AOSP English keyboard endless crash :silly: when I was on CM12.1 with an older device
Dead-neM said:
Used titanium to restore data of system app have always been buggy for me on every phone tablet that i've possessed. TiBu is usefull for data app
Click to expand...
Click to collapse
One of the hard lessons I have learned.
Lawlrus said:
Yeah, I mean I clean flash everything but I know everyone is different.
Click to expand...
Click to collapse
Dead-neM said:
Btw a clean flash doesn't mean to restore data of a previous rom lol
Click to expand...
Click to collapse
Oh lol it never means that! A clean "flash" is no more than 90 seconds to me but a clean "install" means recovering a whole shelf of over a hundred apps from .... the play store .... no the auto re-install only works if i got the same android id
Custom Kernel
I've been using nightlies for quite a while now, since my Nexus One and then my Samsung GS3. I've been reading up on Kernels but there are just so many... and they all say the same thing "Best balance of battery life and performance."
Yes, I could just try all 10 or so out there, but would like to be a little more efficient with my time, so I ask: What do you guys think is a good starting point for trying Kernels? I'm looking for obviously a good balance, but I'm a little more towards the performance side... CM13 has been a little laggy for me, especially with Swapps and rendering backgrounds loaded by chainfire's 500 Firepaper app. And I'll be damned if a colleague's iPhone is faster or more responsive than my Nexus!!!! :laugh:
Franko? ElementalX?
skim7x said:
I've been using nightlies for quite a while now, since my Nexus One and then my Samsung GS3. I've been reading up on Kernels but there are just so many... and they all say the same thing "Best balance of battery life and performance."
Yes, I could just try all 10 or so out there, but would like to be a little more efficient with my time, so I ask: What do you guys think is a good starting point for trying Kernels? I'm looking for obviously a good balance, but I'm a little more towards the performance side... CM13 has been a little laggy for me, especially with Swapps and rendering backgrounds loaded by chainfire's 500 Firepaper app. And I'll be damned if a colleague's iPhone is faster or more responsive than my Nexus!!!! :laugh:
Franko? ElementalX?
Click to expand...
Click to collapse
Try this one https://www.androidfilehost.com/?fid=24499762636000737
This is the latest singularity kernel
Also on post 2 I've post 2 kernel Blackbird and Singularity which in my opinion are the best
I don't like elementalx and Franco but I'm open mind and I'll add link if you find an other good kernel