[DEV][ROM] TeamGalaxyR-Cyanogenmod7-Prealpha Release 3

Search This thread

Aquethys

Retired Forum Moderator
Dec 26, 2011
1,267
796
Colorado
:eek: how soon?!? Me is soooo excited :D:D
It's been slow in our device dev, thanks so much to you guys on getting espy the device! Hopefully he can just modify a little and we will get our cm :)

Sent from my SAMSUNG-SGH-I927R using xda premium
 
:eek: how soon?!? Me is soooo excited :D:D
It's been slow in our device dev, thanks so much to you guys on getting espy the device! Hopefully he can just modify a little and we will get our cm :)

Sent from my SAMSUNG-SGH-I927R using xda premium

I don't know , because you must always remember CM's Rule #1.

The mods can close this thread now , so Epsy can start a new thread without all the mess shown here .

"What else is darkness.....but hate and rage? Xehanort is feeding the dark fires within you, making you fight. You'll go astray again." - Aqua, while talking to Terra about him falling into the darkness.
 

bhargav143

Senior Member
Mar 6, 2011
314
84
Berhampur
Hi!

Here comes a newly compiled CM7.2 from our sources without the erratapatch (Thanks Adam77Root).
Same functionality as the latest AOSP build but without working phonecalls.

cm-7-20120711-UNOFFICIAL-galaxyr.zip

This will be the last that I do on these sources, so let us all try to support Adam77Root and Epsylon3 to make a final and working build!!!

Thanks to u too dude.....
This means... It has wifi,bluetooth, mobile data...working...???
Can somebody confirm... I am still downloading it...

Edit:

Tested this build... its a big leap again... many stuffs are working.... now.. I am using cyanogen...yipiiie...

Sent from my GT-I9103 using xda app-developers app
 
Last edited:

bhargav143

Senior Member
Mar 6, 2011
314
84
Berhampur
Instead of working... I am listing the not working ones... beacause I have not tested the whole system...

Not working:

Wi-Fi
Phone calls(bugged)
Some apps
Camera
Bluetooth


Imporatant Features(Working):

Mobile data
Messaging
Music
Vibration
Sensors
Root access
Many Cyanogen features...
And many more...

But.. I am so much happy... I can't tell u people... thank u all the Devs..especially Adam.... and Epsylon is coming with probably a fully functional build...

Sent from my GT-I9103 using xda app-developers app
 
Last edited:

'cooleagle'

Retired Forum Moderator
Jan 19, 2012
1,899
1,144
Epsylon , it's best that you start your own thread ! That will allow you to have a fresh start :D
+ infinity
It's getting confusing to follow two threads on the same topic.

@Epsylon3
If you start one you can always update the OP with the current status of what's working & what needs to be debugged. Take as many posts of the new thread you deem necessary.

And Matt if it's fine with you & TeamGalaxyR you can lock this thread by posting a link to the new thread in the OP and also post it at the end. :)
 
Last edited:

azhar.munshi

Senior Member
Apr 11, 2011
386
10
i am getting error while installing ro.prob.device etc...

---------- Post added at 11:46 AM ---------- Previous post was at 11:09 AM ----------

iits not booting it stuck on cynogen mod screen
 

Epsylon3

Senior Member
Jan 25, 2008
1,177
4,310
Geneva
tanguy.forumdoandroid.com
I will make a thread tomorrow... i was in kernel and sensors code the whole journey... but now it s time to sleep a bit :)

I dont have pushed the kernel stuff for the moment... i need to clean that... nothing big

but a new build is uploaded.. 14 Jul... changelog available in rom updater and my tpruvot repo on github


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

Aquethys

Retired Forum Moderator
Dec 26, 2011
1,267
796
Colorado
Hi,

I'm trying to edit Adam's update-script to work with my Glide (used a porting guide) and I get an error in CWMR:

format() expected 4 args, got 3


4 arguments? How is that supposed to work?

Thanks!
 

Epsylon3

Senior Member
Jan 25, 2008
1,177
4,310
Geneva
tanguy.forumdoandroid.com
Hi,

I'm trying to edit Adam's update-script to work with my Glide (used a porting guide) and I get an error in CWMR:

format() expected 4 args, got 3


4 arguments? How is that supposed to work?

Thanks!

is the I927 using exactly the same partitions ? i mean, are you able to use Galaxy R custom roms without modifications ?

else, for your problem it was the main change in CWM4/5 (2 years ago) but i dont remember exactly ;) could you remember us which function ?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 19
    HELLO GUYS :D

    I compiled CM7 from newest sources and I would want to see if it works like AOSP

    I've not done any tweaking as of yet because I don't know what will work for the R .

    Features:
    - Theme Chooser (freedom to install any CM7 theme)
    - Ability to take Screenshots directly from Power Menu
    - Extended power menu
    - Allows rebooting normally , to recovery and even bootloader (not applicable)

    Anyway , I need a kind soul to take screenshots (you will be credited)

    Main developers:
    Me
    FranzJesus
    UnknownzD
    And eaglerazor
    ;)

    Here's the status report by bhargav143:
    Instead of working... I am listing the not working ones... beacause I have not tested the whole system...

    Not working:

    Wi-Fi
    Phone calls(bugged)
    Some apps
    Camera
    Bluetooth


    Imporatant Features(Working):

    Mobile data
    Messaging
    Music
    Vibration
    Sensors
    Root access
    Many Cyanogen features...
    And many more...


    DOWNLOAD HERE PEOPLE (thanks to FranzJesus):
    http://dl.dropbox.com/u/3020667/AOSP-GalaxyR/cm-7-20120711-UNOFFICIAL-galaxyr.zip
    14
    Latest Build

    Hi!

    Here comes a newly compiled CM7.2 from our sources without the erratapatch (Thanks Adam77Root).
    Same functionality as the latest AOSP build but without working phonecalls.

    cm-7-20120711-UNOFFICIAL-galaxyr.zip

    This will be the last that I do on these sources, so let us all try to support Adam77Root and Epsylon3 to make a final and working build!!!
    10
    Sad that people who don't have Galaxy R working on rom for it - it will takes ages.

    Would you be kind enough to donate one or money to them ?? :D
    If not, nonconstructive comments best kept to oneself.
    We are very fortunate to have a forum after much debate and even more fortunate to have kind devs doing this for next to nothing.

    Please choose your words carefully in the future. :D

    Cheers !
    9
    I will make a thread tomorrow... i was in kernel and sensors code the whole journey... but now it s time to sleep a bit :)

    I dont have pushed the kernel stuff for the moment... i need to clean that... nothing big

    but a new build is uploaded.. 14 Jul... changelog available in rom updater and my tpruvot repo on github


    Sent from my GT-I9103 using xda app-developers app
    7
    I have found a bug (or better say the config that not yet enabled is wrong) in your github repo for BoardConfig.mk

    https://raw.github.com/EmoBoiix3/android_device_samsung_galaxyr/master/BoardConfig.mk

    # BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00480000
    # BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00780000
    # BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x0cf80000
    # BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x0d020000

    The correct value should be
    # Boot image size is 16384 x 512 bytes = 8388608
    # You can double check it with fdisk -l /dev/block/mmcblk0p9
    BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00800000
    # Recovery image size is 10240 x 512 bytes = 5242880
    # You can double check it with fdisk -l /dev/block/mmcblk0p8
    BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000
    # System image size is 1228800 x 512 bytes = 629145600
    # You can double check it with fdisk -l /dev/block/mmcblk0p2
    BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x25800000
    # User data image size is 4194304 x 512 bytes = 2147483648
    # You can double check it with fdisk -l /dev/block/mmcblk0p6
    BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x80000000

    I know that someone has said the mmcblk0p* size is in 2048 bytes / unit before, however it is wrong as most of the partitions on mmcblk0 are using 512 bytes / unit only. btw I am trying to dump the pit file out of the device ... wish me luck for that :)

    In addition, this is the recovery.fstab that someone provided to me (and I have confirmed that it should be right)
    # mount point fstype device [device2]

    /efs ext4 /dev/block/mmcblk0p1
    /system ext4 /dev/block/mmcblk0p2
    /cache ext4 /dev/block/mmcblk0p3
    /sdcard vfat /dev/block/mmcblk0p4
    /misc emmc /dev/block/mmcblk0p5
    /data ext4 /dev/block/mmcblk0p6
    /recovery emmc /dev/block/mmcblk0p8
    /boot emmc /dev/block/mmcblk0p9
    /prebuilt ext4 /dev/block/mmcblk0p11
    /sd-ext vfat /dev/block/mmcblk1p1