[FUTURE]CM 12.1 Discussion for GT-S7562

[_AE_]

This is ridiculous that developer is afraid to test his ROM. If the screenshots are real may be after some script updation CM 12.1 really works on our device. Waiting for KilnkOne's expert opinion

Just dont want to hard brick my device....soft brick or bootloop is ok:good:

 

[_AE_]

Compare Samsung Galaxy S Duos S7562 vs Samsung Galaxy S Duos 2 S7582

Samsung Galaxy S Duos S7562

Samsung Galaxy S Duos 2 S7582

Differences

Samsung Galaxy S Duos S7562
Rs. 9,380

Samsung Galaxy S Duos 2 S7582
Rs. 7,299

Overview Advantages (Factors To Decide Which Device You Should Buy)
s7562 s7582
Rankings # 2 # 1
Operating System Android, v4.0 (ICS) Android, v4.2 (Jelly Bean)

Battery
Samsung Galaxy S Duos S7562
445 Hours
Samsung Galaxy S Duos 2 S7582
280 Hours

CPU

Samsung Galaxy S Duos S7562
Single Core
Samsung Galaxy S Duos 2 S7582
Dual Cor


Longer Battery Talk Time

Samsung Galaxy S Duos S7562
780 Minutes
Samsung Galaxy S Duos 2 S7582
480 Minutes

Faster CPU

Samsung Galaxy S Duos S7562
1 GHz
Samsung Galaxy S Duos 2 S7582
1.2 GHz

Supports Video Recording

Samsung Galaxy S Duos S7562
640 x 480 px
Samsung Galaxy S Duos 2 S7582
1280 x 720 px

Faster Download Speed

Samsung Galaxy S Duos S7562
7.2 Mbps
Samsung Galaxy S Duos 2 S7582
21 Mbps

General S7562 S7582
Sim Type GSM+GSM GSM+GSM
Dual Sim
Yes Yes
Device Type Smartphone Smartphone
Release Date July, 2012 November, 2013
Design
Dimensions 121.5 x 63.1 x 10.5 mm 121.5 x 63.1 x 10.6 mm
Weight 120 g 118 g
Display
Type Color TFT screen, 16M colors Color TFT screen, 16M colors
Touch
Yes, with Multitouch Yes, with Multitouch
Size 4 inches, 480 x 800 pixels 4 inches, 480 x 800 pixels
PPI ~ 233 PPI ~ 233 PPI
Memory
Internal 4 GB inbuilt, 768 MB RAM 4 GB inbuilt, 768 MB RAM
Card Slot
Yes, upto 32 GB Yes, upto 64 GB
Inbuilt Memory: 1.8 GB user available
Connectivity
GPRS Yes Yes
3G
Yes, 7.2 Mbps Download, 5.76 Mbps Upload Yes, 21 Mbps Download, 5.76 Mbps Upload
Wifi
Yes, with wifi-hotspot Yes, with wifi-hotspot
Bluetooth
Yes, v3.0 Yes, v4.0
USB
Yes, microUSB v2.0 Yes, microUSB v2.0

Camera
Yes, 5 MP with autofocus Yes, 5 MP with autofocus
Features Geo tagging Geo tagging

Video Recording
Yes, 480p @ 30fps Yes, 720p @ 30fps

Flash
LED LED
Front Camera
Yes, VGA (0.3 MP)
Yes, VGA (0.3 MP)
Technical

OS Android, v4.0 (ICS) Android, v4.2 (Jelly

Processor 1 GHz Processor 1.2 GHz, Dual Core Processor

Yes, supports HTML/Flash Yes, supports HTML
Multimedia
Supports MMS, Instant Messaging, Calendar, YouTube Player MMS Email
Yes, with Push Mail
Music
MP3, eAAC+, WMA, WAV MP3, eAAC+, WMA, WAV

Video
MP4, H.263, H.264, WMV MP4, H.263, H.264, WMV

FM Radio
s7562Yes
s7582Yes
Document Reader
s7562Yes
s7582Yes
Extra
GPS
s7562Yes, with A-GPS Support
s7582Yes, with A-GPS Support
Sensors Accelerometer, Compass Accelerometer, Compass
3.5mm Headphone Jack
s7562Yes
s7582Yes
Battery
Size 1500 mAH, Li-ion Battery 1500 mAH, Li-ion Battery
Standby time 18.5 days, 13.8 days on 3G 11.7 days on 3G
Talk time 13 hours, 7.4 hours on 3G 8 hours on 3G
Features
:good:

 

[billysam]

Check out this http://www.smartprix.com/mobiles/sa...g_galaxy_s_duos_2_s7582-c2179_1101od5yknw.php
Theres not much difference in the link

did you get what I said? do you understand difference in chipset and what it means?
the files that you copied from s7582 works for chipset of same make, s7562 chipset is not same. the files and codes are different and works differently. you have not even spend time on the files that you blindly copied, failed to look for simple mistakes that I found just by looking briefly.
you really need to learn before posting or asking people to flash even when I provide enough evidence that it will not work, you still seems to think it's all play over xda? just posting you are not responsible for bricked device of others and don't come blaming you for your own mistakes. it's not fair.

 

[_AE_]

you didn't even read that guide nicely. geez, s7582 is chipset BCM 28145/28155 and a dual core cortex A-9 ours is single core cortex A-5 on chipset Qualcomm MSM7227A Snapdragon S1. totally different architecture. it's never going to work. please remove this.

The big difference is

S7562 S7582​

CPU

1 GHz , 1.2 GHz​

and also
Processor Type

Single-Core Dual-Core​

Samsung Galaxy S Duos S7562
Best Price at eBay
Rs. 12,290
Samsung Galaxy S Duos 2 S7582
Best Price at Shopclues
Rs. 9,999

 

[billysam]

The big difference is

S7562 S7582​

CPU

1 GHz , 1.2 GHz​

and also
Processor Type

Single-Core Dual-Core​

Samsung Galaxy S Duos S7562
Best Price at eBay
Rs. 12,290
Samsung Galaxy S Duos 2 S7582
Best Price at Shopclues
Rs. 9,999

and everything changes because of this

www.gsmarena.com/samsung_galaxy_s_duos_2_s7582-5876.php

www.gsmarena.com/samsung_galaxy_s_duos_s7562-4883.php

read here, you see same chipset? now tell me can you load a motherboard drivers files meant for i7 series motherboard on your old pentium 4 supported motherboard?
it's simple logic, why is it so hard for you to understand?

 

[_AE_]

and everything changes because of this

www.gsmarena.com/samsung_galaxy_s_duos_2_s7582-5876.php

www.gsmarena.com/samsung_galaxy_s_duos_s7562-4883.php

read here, you see same chipset? now tell me can you load a motherboard drivers files meant for i7 series motherboard on your old pentium 4 supported motherboard?
it's simple logic, why is it so hard for you to understand?

S7582: Chipset BCM 28145/28155
S7562: Qualcomm MSM7227A Snapdragon S1

I made using tutorial: http://forum.xda-developers.com/showthread.php?t=2545618

in this tutorial he said don't copy all the files(i have not copied all the files except the ones he said)....

 

[_AE_]

It does not even flash as after fixing mounting points it fails at 80%.

Go to META-INF\com\google\updater script, open using notepad++ ......find 80% and cut the lines

[CODE]run_program("/sbin/busybox","cp","-f","/system/etc/init.d/40int2ext","/tmp");
run_program("/sbin/busybox","cp","-f","/system/etc/init.d/45swap2int","/tmp");
run_program("/sbin/busybox","cp","-f","/system/etc/init.d/swap2int","/tmp");
run_program("/sbin/busybox","cp","-f","/system/etc/init.d/00post-init.sh","/tmp");
run_program("/sbin/busybox","cp","-f","/system/etc/init.d/enable-oc.sh","/tmp");
run_program("/sbin/busybox","cp","-f","/system/etc/init.d/04apps2sd","/tmp");
run_program("/sbin/busybox","cp","-f","/system/etc/init.d/11customsettings","/tmp");
run_program("/sbin/busybox","cp","-f","/system/etc/init.d/50selinuxrelabel","/tmp");

[/CODE]
Do Not cut

run_program("/sbin/busybox","cp","-f","/system/etc/init.d/90userinit","/tmp"); and
run_program("/sbin/busybox","cp","-f","/system/etc/init.d/00banner","/tmp");

 

[_AE_]

I am finally agreed to test it... but i am asking everbody should I test it or not

 

[billysam]

S7582: Chipset BCM 28145/28155
S7562: Qualcomm MSM7227A Snapdragon S1

I made using tutorial: http://forum.xda-developers.com/showthread.php?t=2545618

in this tutorial he said don't copy all the files(i have not copied all the files except the ones he said)....

the guide clearly says, "You can NOT Port different android versions!!!"

---------- Post added at 01:24 PM ---------- Previous post was at 01:18 PM ----------

I am finally agreed to test it... but i am asking everbody should I test it or not

it won't hard brick, if you use the kernel of our device.
the mount points is OK, so it wont flash on wrong partition.

still there are chances you will get bootloop, or stuck on screen. it's recoverable.

 

[_AE_]

the guide clearly says, "You can NOT Port different android versions!!!"

---------- Post added at 01:24 PM ---------- Previous post was at 01:18 PM ----------



it won't hard brick, if you use the kernel of our device.
the mount points is OK, so it wont flash on wrong partition.

still there are chances you will get bootloop, or stuck on screen. it's recoverable.

Thanks......:laugh::good::fingers-crossed:

 

[billysam]

Thanks......:laugh::good::fingers-crossed:

don't forget to take nandroid backup.

 

[_AE_]

don't forget to take nandroid backup.

If u said theres clearly written u cant port different versions,then why i need to test it ?

 

[_AE_]

rom porters help me on porting cm12.1 for our S7562.........till then check theme....plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz

 

[KlinkOnE]

Everything is said now i think....

What have we learned?

Reading, studying and comparing leads to success or prevents failure.
Indeed you are responsible for what you are doing and what happens in consequence.
(If someone bricks his device you are responsible for that though he cant prosecute for this)

So do you delete the thread or should i?
EDIT: ok its the cm12.1 discussion thread now and i am fine with that thanks!
EDIT2: could you please remove the "unofficial" from the title

 

[eng4r]

so its working ????

 

[KlinkOnE]

so its working ????

nobody knows
chances for boot are propably 1:1000000
chances for anything after boot are propably 1:1000000

the right answer is almost impossible

 

[KlinkOnE]

here is a good reference for those willing to build cm12(.1) from source for s7562
https://github.com/HtcLegacy

Take a look at the pico repos to get an idea of what is necessary!
This doesnt necessarely mean we can take this as is!

Why pico?
-> msm7x27a -> PMEM -> 3.0.x kernel -> cm12.1

whole lotta work!
good luck

 

[pk2507]

cm12.1

here is a good reference for those willing to build cm12(.1) from source for s7562


Take a look at the pico repos to get an idea of what is necessary!
This doesnt necessarely mean we can take this as is!

Why pico?
-> msm7x27a -> PMEM -> 3.0.x kernel -> cm12.1

whole lotta work!
good luck

@KlinkOnE Dude i am back.....i tired a lot to built cm12 from source using majonez device tree..even...tried omni5.1...but ...ended up with too much build errors..now syncing back cm12.1 sources....could you be more specific towards msm7x27a>PMEM>3.0.x kernel>cm12.1 .

 

[KlinkOnE]

@KlinkOnE Dude i am back.....i tired a lot to built cm12 from source using majonez device tree..even...tried omni5.1...but ...ended up with too much build errors..now syncing back cm12.1 sources....could you be more specific towards msm7x27a>PMEM>3.0.x kernel>cm12.1 .

What I want to say is that the basic chipset hardware, the kernel version and the used memory allocator are same as our device.
That's why it can be used as a reference.
Of course several updates are required for cm12+ which can be followed in the pico repos.
For example the deprecated pmem memory allocator has to be exchanged with ion.
Youll find the ion commits for pico in there kernel repo. These changes have to be adapted for our kernel.

as I said much work is to be done which even may not lead to success.

good luck anyway

 

[pk2507]

What I want to say is that the basic chipset hardware, the kernel version and the used memory allocator are same as our device.
That's why it can be used as a reference.
Of course several updates are required for cm12+ which can be followed in the pico repos.
For example the deprecated pmem memory allocator has to be exchanged with ion.
Youll find the ion commits for pico in there kernel repo. These changes have to be adapted for our kernel.

as I said much work is to be done which even may not lead to success.

good luck anyway

i tired porting from pico but no luck ...i am not building.....