[ROM][GT-I9300][JB][4.2.2] CyanogenMod 10.1 official nightlies // discussion thread

Search This thread

AaronMichael

Senior Member
Dec 22, 2012
249
47
Jakarta
Re: [ROM][GT-I9300][JB][4.2.1] CyanogenMod 10.1 official nightlies // discussion thre

You say that now... I wonder if you'll say that when the s4 is announced / released.

Sent from my GT-I9300

I've somewhat regretted buying Samsung. I had bad experiences with Samsung phones before the smartphone days. I thought I'd give Samsung another chance, also because the S3 is said to be good.

The amount of problems S3 is having now even in stock form...just a bit disappointing for an expensive smartphone. This phone isn't $100..its a premium phone with a premium price but lacks in its field...

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

tux821

Senior Member
May 25, 2012
212
46
Re: [ROM][GT-I9300][JB][4.2.1] CyanogenMod 10.1 official nightlies // discussion thre

Last few weeks I get some spontaneous soft reboots, about one a day.
Just in the middle of something, bam reboot.. Its not a normal reboot because my Sim pin is not asked.

I always upgrade to the latest nightly using the CM updater.
I did make logcats but I can't pin down the problem, see below for the part where I think the crash/reboot begins (Fatal Exception of the Activity Manager).

Any tips or me too's on this one?

Code:
02-13 09:16:05.600 W/Settings(2993): Setting auto_time_zone has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.

02-13 09:16:05.600 D/AlarmManagerService(2275): Kernel timezone updated to -60 minutes west of GMT

02-13 09:16:05.720 D/BluetoothAdapter(2874): 1092788448: getState() :* mService = null. Returning STATE_OFF

02-13 09:16:05.865 D/LittleFluffyLocationLibrary(22902): PassiveLocationChangedReceiver: Distance from last reading: 0m

02-13 09:16:05.870 D/LittleFluffyLocationLibrary(22902): PassiveLocationChangedReceiver: Storing location update, lat=52.28155 long=5.182101 accuracy=4 time=1360743366000(09:16.06, wo)

02-13 09:16:06.150 W/dalvikvm(2275): threadid=15: thread exiting with uncaught exception (group=0x40ddb930)

02-13 09:16:06.165 E/AndroidRuntime(2275): *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager

02-13 09:16:06.165 E/AndroidRuntime(2275): java.lang.IllegalArgumentException

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Parcel.nativeAppendFrom(Native Method)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Parcel.appendFrom(Parcel.java:428)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Bundle.writeToParcel(Bundle.java:1613)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Parcel.writeBundle(Parcel.java:605)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.location.Location.writeToParcel(Location.java:903)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Parcel.writeParcelable(Parcel.java:1254)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Parcel.writeValue(Parcel.java:1173)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Parcel.writeMapInternal(Parcel.java:591)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Bundle.writeToParcel(Bundle.java:1619)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Parcel.writeBundle(Parcel.java:605)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.location.Location.writeToParcel(Location.java:903)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Parcel.writeParcelable(Parcel.java:1254)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Parcel.writeValue(Parcel.java:1173)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Parcel.writeMapInternal(Parcel.java:591)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Bundle.writeToParcel(Bundle.java:1619)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Parcel.writeBundle(Parcel.java:605)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.content.Intent.writeToParcel(Intent.java:6708)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.app.ApplicationThreadProxy.scheduleReceiver(ApplicationThreadNative.java:763)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at com.android.server.am.BroadcastQueue.processCurBroadcastLocked(BroadcastQueue.java:230)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at com.android.server.am.BroadcastQueue.processNextBroadcast(BroadcastQueue.java:777)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at com.android.server.am.BroadcastQueue$1.handleMessage(BroadcastQueue.java:139)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Handler.dispatchMessage(Handler.java:99)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at android.os.Looper.loop(Looper.java:137)

02-13 09:16:06.165 E/AndroidRuntime(2275): ******* at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1486)

02-13 09:16:06.200 I/Process (2275): Sending signal. PID: 2275 SIG: 9

02-13 09:16:06.205 D/dalvikvm(3035): GC_CONCURRENT freed 404K, 22% free 3257K/4176K, paused 3ms+2ms, total 70ms

02-13 09:16:06.350 I/ServiceManager(1904): service 'throttle' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'fm_receiver' died

02-13 09:16:06.350 W/Sensors (2993): sensorservice died [0x5d791470]

02-13 09:16:06.350 I/ServiceManager(1904): service 'updatelock' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'fm_transmitter' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'profile' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'notification' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'devicestoragemonitor' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'location' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'country_detector' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'search' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'dropbox' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'wallpaper' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'audio' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'usb' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'serial' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'uimode' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'backup' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'appwidget' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'diskstats' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'samplingprofiler' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'commontime_management' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'dreams' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'assetredirection' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'servicediscovery' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'connectivity' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'entropy' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'alarm' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'vibrator' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'scheduling_policy' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'telephony.registry' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'sensorservice' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'netpolicy' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'account' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'package' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'activity' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'statusbar' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'gfxinfo' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'accessibility' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'batteryinfo' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'cpuinfo' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'input' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'display' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'netstats' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'lock_settings' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'clipboard' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'input_method' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'permission' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'user' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'usagestats' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'dbinfo' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'content' died

02-13 09:16:06.350 D/SurfaceFlinger(1909): Screen acquired, type=0 flinger=0x40730318

02-13 09:16:06.350 D/SurfaceFlinger(1909):* screen was previously acquired

02-13 09:16:06.350 I/ServiceManager(1904): service 'meminfo' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'window' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'bluetooth_manager' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'device_policy' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'mount' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'power' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'hardware' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'wifip2p' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'battery' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'network_management' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'wifi' died

02-13 09:16:06.350 I/ServiceManager(1904): service 'textservices' died

02-13 09:16:06.350 W/Sensors (3035): sensorservice died [0x5d7a7e80]

02-13 09:16:06.350 W/Sensors (25435): sensorservice died [0x58cdd9a8]

02-13 09:16:06.350 W/AudioFlinger(18946): power manager service died !!!

02-13 09:16:06.350 E/StrictMode(3035): RemoteException handling StrictMode violation

02-13 09:16:06.350 E/StrictMode(3035): android.os.DeadObjectException

02-13 09:16:06.350 E/StrictMode(3035): **** at android.os.BinderProxy.transact(Native Method)

02-13 09:16:06.350 E/StrictMode(3035): **** at android.app.ActivityManagerProxy.handleApplicationStrictModeViolation(ActivityManagerNative.java:3359)

02-13 09:16:06.350 E/StrictMode(3035): **** at android.os.StrictMode$4.run(StrictMode.java:1375)

02-13 09:16:06.355 E/BufferQueue(1909): [StatusBar] dequeueBuffer: SurfaceTexture has been abandoned!

02-13 09:16:06.355 E/******* (2874): void __egl_platform_dequeue_buffer(egl_surface*):1200 [EGL-ERROR] failed to dequeue buffer from native window (0x51768490); err = -19, buf = 0x56fa4e44

..
 
Last edited:

bi00

Member
Feb 23, 2010
12
0
CIFS Support

Hello dudes,
yesterday I tried to get CFISManager and/or MountManager working. But I did not work :( Also tried via terminal, also no luck.

So my question is if CFIS is basicly working and if it is do I have to use special mount points or something like that ?

With a SMBBrowser I can connect to my samba share...
 
Last edited:

selimozbas

Senior Member
Aug 4, 2011
161
10
Hello,

I install new nightly (20130213) today. But I have big problem. I can't hear any sound on incoming calls or outgoing calls
 

Tantawi

Senior Member
Dec 1, 2007
111
39
Stockholm
Hello,

I install new nightly (20130213) today. But I have big problem. I can't hear any sound on incoming calls or outgoing calls

I had the same problem, fixed it by doing all of these (don't know which step fixed it exactly):

1- Wiping cache.
2- Wiping dalvik cache.
3- Turning off and removing the battery for 3 seconds then turn it on again.

Good luck.
 
  • Like
Reactions: selimozbas

selimozbas

Senior Member
Aug 4, 2011
161
10
Thanks :) solved

---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------

I think removing the battery solve the problem.
Because firstly I try to wipe cache/dakvik cache and only this step not solved
 

Zatta

Inactive Recognized Developer / Contributor
Dec 22, 2010
2,177
1,222
Sneek

AaronMichael

Senior Member
Dec 22, 2012
249
47
Jakarta
Re: [ROM][GT-I9300][JB][4.2.1] CyanogenMod 10.1 official nightlies // discussion thre

Btw guys is the bug on setting timezone automatically still not fixed? Cause it still puts me in GMT no matter what...

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

Bambushacker

Senior Member
Oct 26, 2012
51
7
I think Samsung s3 is a great phone! But only when its rooted. :D
All the Jellybean roms... the most of them, are ultra smooth and stable, aaand bugfree.

And now since 02_12, CM is nearly bugfree. I only have two issuses:

When i play music, and want to skip a track on the volumebuttons, sometimes it freezes the player.

And the second is when i use gps. Without Wlan detection, all is fine, but after using one single time the wlan detection, the gps doesnt go off again, and google maps needs a lot of energy. Only a reboot shuts the gps off.

But apart from these bugs, CM is ultra fine, smooth and battery friendly.
There is now rom who sleeps so deep!!!

So keep *****ng support CM!!!

Screenshot_2013-02-13-10-33-16.jpg

Screenshot_2013-02-13-10-33-09.jpg
 
  • Like
Reactions: Erahgon

capricornian

Senior Member
Jul 15, 2012
487
182
Mumbai
Anybody else also facing the brightness issue? its not changing.. stuck up at one level..
using CM 10.1 and stock CM kernel..
Edit: not facing the problem on the latest nightly..
Edit again: problem started again..
 
Last edited:
  • Like
Reactions: rudolf13

Coruja747

Senior Member
Nov 26, 2008
179
49
devs, someone could fix a simple pt-br translation error on cLock options menu here plz?
<string name="weather_show_timestamp_title">Exbir horário</string> -> Exibir horário

and add some new translations from this latest change here:
<string name="expanded_desktop_disabled">Off</string> -> Desligado
<string name="expanded_desktop_status_bar">Status bar visible</string> -> Barra de status visível
<string name="expanded_desktop_no_status_bar">Status bar hidden</string> -> Barra de status oculta
 

temasek

Senior Member
Feb 2, 2010
23,624
85,271
Singapore
Re: [ROM][GT-I9300][JB][4.2.1] CyanogenMod 10.1 official nightlies // discussion thre

devs, someone could fix a simple pt-br translation error on cLock options menu here plz?
<string name="weather_show_timestamp_title">Exbir horário</string> -> Exibir horário

and add some new translations from this latest change here:
<string name="expanded_desktop_disabled">Off</string> -> Desligado
<string name="expanded_desktop_status_bar">Status bar visible</string> -> Barra de status visível
<string name="expanded_desktop_no_status_bar">Status bar hidden</string> -> Barra de status oculta

Sure

If no one does it yet, I'll submit the changes after my supper.

EDIT: Done.

http://review.cyanogenmod.org/#/c/31838/
http://review.cyanogenmod.org/#/c/31839/
 
Last edited:
  • Like
Reactions: power461 and hteles

bi00

Member
Feb 23, 2010
12
0
Anybody can tell me if I did something wrong or there are issues with CFIS on CM10.1 ?

Hello dudes,
yesterday I tried to get CFISManager and/or MountManager working. But I did not work :( Also tried via terminal, also no luck.

So my question is if CFIS is basicly working and if it is do I have to use special mount points or something like that ?

With a SMBBrowser I can connect to my samba share...
 

AaronMichael

Senior Member
Dec 22, 2012
249
47
Jakarta
Re: [ROM][GT-I9300][JB][4.2.1] CyanogenMod 10.1 official nightlies // discussion thre

i'm seeing it too! though for some reason the alarm still goes off at the time set before the bug hits.

I just turned of auto setting of the timezone and manually set it to counter the issue. It isn't something big, but it is a bit of a hassle to remember to change timezones when I travel.

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

Top Liked Posts

  • There are no posts matching your filters.
  • 484
    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.2 (JB), which is designed to increase performance and reliability over stock Android for your device.

    Code:
    #include 
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     *
     * Submitting bug reports on nightly builds is the leading 
     * cause of male impotence.
     */

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    IMPORTANT INFORMATIONS


    We'll not support users and answer questions from users which:
    - are running a custom kernel
    - have flashed mods
    - modified system files
    - didn't follow our intructions word by word
    - are unfriendly

    Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
    Your mod => your problem!



    Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/I9300_Info


    First time installing CyanogenMod 10.1 to your Galaxy S III, or coming from another ROM:
    - Read known issues ans FAQs
    - Make sure you're running a proper working ClockworkMod-Recovery
    - Copy GApps and CM10.1 ZIPs to your SDCard
    - Boot into Recovery
    - Flash CM10.1 zip from SDCard
    - Flash GApps zip from SDCard
    - DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
    - Reboot
    - Don't restore system data using Titanium Backup!
    - Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!

    Upgrading from earlier version of CyanogenMod 10.1:
    - Copy CM10.1 ZIP to your SDCard
    - Boot into Recovery
    - Flash CM10.1 zip from SDCard
    - Reboot

    Upgrading from CyanogenMod 10:
    - Read known issues ans FAQs
    - Copy GApps and CM10.1 ZIPs to your SDCard
    - Boot into Recovery
    - Flash CM10.1 zip from SDCard
    - Flash GApps zip from SDCard
    - Reboot
    - Wipe data of clock app
    - Reset everything under Settings -> Date & Time otherwise editing alarms might cause FCs


    CM10.1 official nightly builds:
    http://www.get.cm/?device=i9300

    Google Apps:
    http://goo.im/gapps

    ClockworkMod Recovery:
    Heimdall: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.2.7-i9300.img (6.0.2.7, Touch)
    Odin: http://d-h.st/dO5 (6.0.1.9, Touch)

    http://changelog.bbqdroid.org/#i9300/cm10.1/next

    TEAMHACKSUNG SUPPORT CHAT
    Webchat: http://webchat.freenode.net/?channels=teamhacksung-support

    Server: chat.freenode.net
    Channel: #teamhacksung-support

    If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
    This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
    Open-Source doesn't meant Out-of-Respect!!!

    1noTtl.png
    7orcIl.png
    I05ZMl.jpg
    kFpQ5l.png



    If you want to donate a few bucks for the work we're doing in our freetime:



    Thanks to all donators!
    97
    If nothing goes wrong you'll have the first official nightly build by tomorrow.
    69
    Yes +1 i hope @XpLoDWilD can help us here :D

    Sent from my GT-I9300 using xda premium

    I will.
    68
    plody seems to have fixed bluetooth.
    tomorrows build then. ;)

    And now I fixed the Camera crashing too :D
    62
    new build up.
    happy calling.