• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ROM] [JB 4.3] Project Equilibrium

Adam77Root

Inactive Recognized Developer
Jul 3, 2012
2,535
11,160
0
**This OP is still a stub.**

Download link: http://www6.zippyshare.com/v/53583730/file.html

-More to come.-
-Suggestions for editing are welcome!-

XDA:DevDB Information
Project Equilibrium i9103, a ROM for the Samsung Galaxy R i9103

Contributors
Adam77Root, Grarak, Disturbed™, Tha TechnoCrat, CallMeVentus
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Stock ICS 4.0.4 (preferably Indian XWLP8)
Based On: CyanogenMod 10.2

Version Information
Status: Alpha

Created 2013-09-24
Last Updated 2013-10-15
 

Nikhil

Elite Member
Sep 26, 2012
1,326
2,167
113
Ahmedabad
First Impression : Great Rom (Screenshots attached)
Thank you @Adam77Root for this Rom.
This Rom like PAC MAN and other custom roms is having the same problem which we also have in CM 10.2 too i.e. After Reboot, it stuck at Galaxy R Screen. no matter what we do, the device doesnt boots up again. :(
this is the only thing that is keeping many users from using 4.3.
I know you dont own Galaxy R anymore and it is difficult to do development but is there any chance that you could solve this "Stuck at Galaxy R Screen" problem?
 

Attachments

D™

Senior Member
First Impression : Great Rom (Screenshots attached)
Thank you @Adam77Root for this Rom.
This Rom like PAC MAN and other custom roms is having the same problem which we also have in CM 10.2 too i.e. After Reboot, it stuck at Galaxy R Screen. no matter what we do, the device doesnt boots up again. :(
this is the only thing that is keeping many users from using 4.3.
I know you dont own Galaxy R anymore and it is difficult to do development but is there any chance that you could solve this "Stuck at Galaxy R Screen" problem?
As its a new project of Team Equilibrium. If possible, try to Provide Log-cat to Team Equilibrium. BTW, Grarak, callmeventus & Tha Technocrat can also help in this regard, if you will provide Log-Cat.;)

BTW, thanks for the screenies.. Really liked that.. ;)
 
Last edited:
  • Like
Reactions: Nikhil

Nikhil

Elite Member
Sep 26, 2012
1,326
2,167
113
Ahmedabad
@Nikhil whenever your phone is stuck at the galaxy logo. Press the power button for 10 seconds. Hard reboot is a workaround until we can find a reason for this problem . If that doesn't then take out the battery and restart the phone.
I am doing the same:D
Sent from my GT-I9103 using
xda app-developers app
Not working for me.
tried hard reboot many times.
tried removing battery
tried clearing dalvik caches
tried rebooting from recovery
tried normal shut down and manually booting.
nothing works for me. :(
i wonder how it is working for you. :confused:
 

CallMeVentus

Senior Member
Jul 25, 2011
10,094
2,839
0
Singapore
www.youtube.com
Here you go. Logcat attached. Hope this help.
Code:
09-24 20:04:12.366 W/ActivityManager(  405): Permission denied: checkComponentPermission() owningUid=10014
09-24 20:04:12.366
W/BroadcastQueue(  405): Permission Denial: broadcasting Intent { act=notif_in_use_cancel flg=0x10 } from com.google.android.deskclock (pid=7027, uid=10055) is not exported from uid 10014 due to receiver com.android.deskclock/.timer.TimerReceiver
09-24 20:04:16.406 W/ActivityManager(  405): Permission denied: checkComponentPermission() owningUid=10014
09-24 20:04:16.406 W/BroadcastQueue(  405): Permission Denial: broadcasting Intent { act=notif_in_use_show flg=0x10 } from com.google.android.deskclock (pid=7027, uid=10055) is not exported from uid 10014 due to receiver com.android.deskclock/.timer.TimerReceiver
09-24 20:04:16.496 W/ActivityManager(  405): Permission denied: checkComponentPermission() owningUid=10014
09-24 20:04:16.496 W/ActivityManager(  405): Permission denied: checkComponentPermission() owningUid=10014
09-24 20:04:16.496 W/dalvikvm( 7027): threadid=12: thread exiting with uncaught exception (group=0x41def700)
09-24 20:04:16.496 W/ActivityManager(  405): Permission Denial: opening provider com.android.deskclock.AlarmProvider from ProcessRecord{422b45f0 7027:com.google.android.deskclock/u0a10055} (pid=7027, uid=10055) that is not exported from uid 10014
The clock alarm service has been denied permission from the start, we'll look into it.
 

Tha TechnoCrat

Senior Member
May 28, 2012
1,553
978
0
24
▂ ▃ ▅ ▆ █ Likes:XDA,The Weeknd
Not working for me.
tried hard reboot many times.
tried removing battery
tried clearing dalvik caches
tried rebooting from recovery
tried normal shut down and manually booting.
nothing works for me. :(
i wonder how it is working for you. :confused:
Which baseband? I have XXLQ3

"Thanks button is just to avoid "THANKS" posts in threads. Nothing more than that. Don't ask in signature or post for it and defeat the purpose why it was introduced"
 

CallMeVentus

Senior Member
Jul 25, 2011
10,094
2,839
0
Singapore
www.youtube.com
Not working for me.
tried hard reboot many times.
tried removing battery
tried clearing dalvik caches
tried rebooting from recovery
tried normal shut down and manually booting.
nothing works for me. :(
i wonder how it is working for you. :confused:
Have you tried mounting /system and /data prior to installation?

You wouldn't care where I sent this message from.