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

Search This thread
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
 
Last edited:
M

m.kochan10

Guest
No boot, freeze on splash screen :(

Sorry I cannot provide a logcatfile because my sgr won't turn on when usb/charger is plugged. (Once I see the splash screen and release power button booting process stops immediately and returns to charging screen. No such problems on stock though)
 
Last edited:
M

m.kochan10

Guest
Of course, u can easily enter recovery and flash rom / restore backup in a regular way. It's not a problem at all.

It's just no way to provide a logcat file. To do it u must try to boot your system while connected to usb and this seems impossible here.

Sent from my GT-I9103 using xda premium
 
Last edited:
Of course, u can easily enter recovery and flash rom / restore backup in a regular way. It's not a problem at all.

It's just no way to provide a logcat file. To do it u must try to boot your system while connected to usb and this seems impossible here.

Sent from my GT-I9103 using xda premium

Can you try to replace the boot.img in my CM7 with the AOSP's boot.img ?

Herpderp Defy.
 
  • Like
Reactions: markchen
M

m.kochan10

Guest
EDIT2: Replacing kernel with the one from last AOSP didn't make any difference....actually it did one, namely: Booting process stops on a splash screen but then phone boots into recovery mode automatically by itself. :)

Sent from my GT-I9103 using xda premium
 
Last edited:

sarun_biotech

Senior Member
Jan 12, 2012
212
112
Bangalore
Can you try to replace the boot.img in my CM7 with the AOSP's boot.img ?

Herpderp Defy.

I just replaced the boot.img from the AOSP release 2 with the one on cm7 and flashed it.

after reboot, it shows the splash screen and then goes back to CWM recovery...

:(

EDIT : Same result when tried with the boot image from release 1.
 
Last edited:

sarun_biotech

Senior Member
Jan 12, 2012
212
112
Bangalore
Sad that people who don't have Galaxy R working on rom for it - it will takes ages.

Actually its sad for "us" sgr users that these talented devs dont have an sgr for testing. And thats y the non-devs/testers help as much they can to find the issues and get them logs.

Sent from my GT-I9103 using xda premium
 

s4sixty

Senior Member
Apr 22, 2007
147
105
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 !
 

'cooleagle'

Retired Forum Moderator
Jan 19, 2012
1,899
1,144
Sad that people who don't have Galaxy R working on rom for it - it will takes ages.

How did you know EmoBoiix3 doesn't have a R ? :rolleyes:
I know he has access(he doesn't use it personally though) to one but for his own valid reasons he can't use it for testing.

I assume you have a R, you should to try to cook some custom ROMs forget CM7 to get an idea how many aspirins they might have to take to get one ROM working correctly.

Don't you think its selfless of them to make ROMs for a device which they themselves don't use/have ?
About the time taken kindly don't ask for ETA's on this forum, it will be stated by the dev themselves when it'll be released.

I don't think statements like these add anything to the forum.
 
Last edited:
  • Like
Reactions: CallMeVentus
M

m.kochan10

Guest
I've tried....but it seems like there's simply no way to switch on your device (after you've flashed rom) while you're connected to PC via usb.

1)I switch off the phone and immediately get charging screen (no animation, just a battery pic)

2)Open cmd,
a) type: adb logcat > logfile.txt ,
b) immediately get information - "waiting for device"

3) Press power button until I see splash screen
4)Once I release the power button booting process stops and charging screen appears instead.

No problems with entering both DM and RM. Such problem doesn't exist on stock. I've no idea how to bypass it.
 

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