Originally Posted by thracemerin

Did you happen to also install this? https://play.google.com/store/apps/d...cmthcm91bmQiXQ..

It's a fix for Hacksync for JB.

Yes, when you install Haxsync it also asks to install that.

I really don't know what is happening.
No need to mention that phone gets really hot.
Up to 10-20120729-EXPERIMENTAL-i9100-CODEWORKX it didn't happened.

I will try a new clean install.

Originally Posted by mirdones

Yes, when you install Haxsync it also asks to install that.

I really don't know what is happening.
No need to mention that phone gets really hot.
Up to 10-20120729-EXPERIMENTAL-i9100-CODEWORKX it didn't happened.

I will try a new clean install.

It sounds like an app is bugged, try installing Better Battery stats (there's a free version on XDA) and leaving it for a few hours then getting a screen shot of Kernel Wakelocks and Partial Wakelocks. That will make it easier for use to help you track down the culprit.

Originally Posted by thracemerin

It sounds like an app is bugged, try installing Better Battery stats (there's a free version on XDA) and leaving it for a few hours then getting a screen shot of Kernel Wakelocks and Partial Wakelocks. That will make it easier for use to help you track down the culprit.

Yes, use better battery stats. But listen, don't ever post screenshots of it, instead use the built in feature to export a log. A .tex file will be created at [Internal memory] (/storage/sdcard0).

I think the issue with the mediascanner is not related to CM10, but to CWM 6 and the new way of making a nandroid backup. The new backup format saves a lot of files called blobs instead of just 9 files in CWM 5. So the mediascanner has to scan all these files in the blobs on every reboot. I tested it by deleting the blobs (be careful, all your backups will be gone!) and the mediascanner needs now 2 Minutes instead of 6 Minutes after each reboot.

I couldn't disable 13 apps at boot autostart by optimizer tool due "root not allowed". Anyone w/ idea about this? Or maybe some suggest by manual editing any file(s) ?

Sent from my GT-I9100 using xda app-developers app

Originally Posted by DSC05

I think the issue with the mediascanner is not related to CM10, but to CWM 6 and the new way of making a nandroid backup. The new backup format saves a lot of files called blobs instead of just 9 files in CWM 5. So the mediascanner has to scan all these files in the blobs on every reboot. I tested it by deleting the blobs (be careful, all your backups will be gone!) and the mediascanner needs now 2 Minutes instead of 6 Minutes after each reboot.

In future versions of CWM recovery, options for backup formats will be added. Not a quote, but an abstract of the creator's tweet.

Originally Posted by DSC05

I think the issue with the mediascanner is not related to CM10, but to CWM 6 and the new way of making a nandroid backup. The new backup format saves a lot of files called blobs instead of just 9 files in CWM 5. So the mediascanner has to scan all these files in the blobs on every reboot. I tested it by deleting the blobs (be careful, all your backups will be gone!) and the mediascanner needs now 2 Minutes instead of 6 Minutes after each reboot.

Hence why there's a .nomedia file in my cwm folder

Originally Posted by wipian

Hence why there's a .nomedia file in my cwm folder

Life could be so easy

Agree with that. New way (blobs) may be ok for saving space on sd, but it is failure in terms of switching from diferent generation backups... I hope old way will be posible eith 6.x, really...

Originally Posted by MiKenning

I very much enjoy this ROM. Seriously, it's given my phone a new lease of life. Such a fast operating system and that's no exaggeration.

I have discovered a few bugs, and it seems to have inherited them from the CM9 nightlies;

1) When playing music and a notification pops up, the music volume drops (as per usual) and stays low after the notification. I have read up and people have acknowledged this, but I'm just making it clear it has been inherited.
2) When the phone goes black, I use the home button to wake it up and the screen I was initially on goes as the phone registers the pressing of the home button as a command to go to the home screen, in stead of simply waking up the phone.
3) The notification center seems a bit laggy too. I understand we're early on though.

If I can make a suggestion, on the Galaxy Nexus you can swipe your finger up from the home button and voila, google search. Anyway you can implement a gesture in order to get to the search from anywhere?

Totally agree with point 2, gets quite annoying I hope this gets fixed or someone knows how to stop it.

Sent from my Jelly Beaned Galaxy S2

---------- Post added at 09:16 AM ---------- Previous post was at 09:14 AM ----------

Originally Posted by zee54

I too am experiencing the same issues as mentioned in #2 by MiKenning.

Basically when I'm using the phone and its on any screen but the home screen and then screen time out kicks in, if I then quickly press the home button to wake the screen up again rather then just turning the screen back on to to what I was originally on it closes that screen and return me to the home screen. As MiKenning said, it is as if it has registered the pressing the home button as a command to return to the home screen instead of just turning the screen back on.

This is obviously only when you have a phone/screen lock delay and you press the home button before your phone has locked itself. Once the phone has locked it works fine and pressing the home button reactivates the screen to the lock screen.

It's a bit of an annoying problem because if I'm viewing a webpage or something and the screen turns off, pressing the home button turn it back on and takes me back to the home screen every time and I have to go back through the recent apps to get back to my webpage.

Exactly what it does for me.

Sent from my Jelly Beaned Galaxy S2