Develop Bugs

[REQUEST] MBR/partitions layout for 16GB version Galaxy S

Hey
As some maybe know I'm working on a lag fix for our Galaxy S.
This lag fix uses ext4 as native filesystem directly on the internal SD to replace rfs.
Features and description here
I'm coding the migration procedure right now and just figured that I need the partition layout of 16GB models to support them
Here is how you can get this data (as root)
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mbr.bin bs=512 count=1
This command will produce a little file describing how your Galaxy S partitions are arranged. You'll find this file as "mbr.bin" in the SD mounted on your computer.
It does not contain any personal information.
required too, the result of :
Code:
cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size
Thanks !
Sample partition layout dump of the 8GB version :
Code:
$ sfdisk -d mbr_samsung
# partition table of mbr_samsung
unit: sectors
mbr_samsung1 : start= 64, size= 12124096, Id= c
mbr_samsung2 : start= 12124160, size= 3932160, Id= c
mbr_samsung3 : start= 0, size= 0, Id= 0
mbr_samsung4 : start= 0, size= 0, Id= 0

cant open for read mmcblk0 .. Egh.. i hate terminal on android

andrewluecke said:
cant open for read mmcblk0 .. Egh.. i hate terminal on android
Click to expand...
Click to collapse
This should be no problem as root

Egh.. Someone else should do it then.. My phone isn't rooted atm

Hey supercurio
Just wondering if you have done any speed testing at all on native EXT4?
Does the phone lock up when writing large files?

Here's mine. Just FYI, not sure if it matters, but i'm on JP3 with the "one click" lag fix.
Also, I'd be happy to beta test your fix on my 16gb SGS. I've pretty much tried them all

I9000 16GB - MBR layout
Here's from a Galaxy S running JM5 + Samset1.9f

I gave this a try on my 16GB SGS
Double checked the syntax and its telling me:
dd: can't open "/dev/block/mmcblk0': permission denied.
Im rooted with su also

supercurio said:
This should be no problem as root
Click to expand...
Click to collapse
well i'm rooted and using terminal emulator and ADB through my PC gets the same result as he posted.
*EDIT - Here's mine sorry rebooted and it ran just fine. this is JM2 with the one click lag fix just for the info.
If it matters Bell vibrant i9000m 16gb model.
Goodluck

Thank you Spybreak and titovic !
Both your mbr are bit-identical, this is a good news
I guess I need another value to detect which hardware I deal with :
Code:
cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size
Thx again
For the record, here is the partition table of your devices :
Code:
$ sfdisk -d mbr-16Go
# partition table of mbr-16Go
unit: sectors
mbr-16Go1 : start= 64, size= 28180416, Id= c
mbr-16Go2 : start= 28180480, size= 3932160, Id= c
mbr-16Go3 : start= 0, size= 0, Id= 0
mbr-16Go4 : start= 0, size= 0, Id= 0
@RyanZA about tests, I played about 3 hours with my device formatted as native ext2.
I was quite surprised by the responsiveness even when installing apps. I did not thought that the difference would be so drastic
I'll do extensive tests to find the best settings.
My goal is to preserve a maximum of interactivity, by consequence it will lower the benchmark settings a bit.
Here is an example of Quadrant run on /data as ext2 (no settings customization)
Note : I used ext2 because my e2fsprogs produced by default ext4 and ext3 formats that the old 2.6.29 drivers were not able to read
PS :
Quadrant score will theoretically always be lower than those obtained with mount -o loop because the filesystem honors fsyncs(), and SQLite database used in Android use fsync big time (and there is a reason why!)

Bell i9000M, rooted, JH2.
New request:
31260672
Question: why journalized fs on a flash device though?

canadian_psyko said:
Bell i9000M, rooted, JH2.
New request:
31260672
Question: why journalized fs on a flash device though?
Click to expand...
Click to collapse
Because you can corrupt a filesystem on flash exactly the same way that on a hard drive :
Kernel driver crash / phone lockup
Abrupt power down (remove the battery)
Abrupt reboot, pressing a combination of keys.
The flash disk here is presented as block, so it looks like a hard drive to the filesystem.
PS : thansk for your 31260672

wow this looks promising. but why don't you consider using YAFFS2 which is also used in Nexus One? havent heard anyone complaining of our kind of lag in the N1

+1, seems a reasonable choice. For testing anyway.

Agreed with the above, most likely YAFFS2 should be used, especially since Google decided it's the way to go =)

supercurio said:
Thank you Spybreak and titovic !
Both your mbr are bit-identical, this is a good news
I guess I need another value to detect which hardware I deal with :
Code:
cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size
Thx again
Click to expand...
Click to collapse
Here's mine from a 16gb i9000 (singapore version) with JM5 and pit512. Won't the pit file used to flash your ROM affect this, or at least the original data you requested...?
Code:
# cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size
32112640
Also, attached is my mbr.bin from the 16gb phone mentioned above.
I like the idea of yaffs also, but would require custom kernels.
I'm glad to see someone working on this, I think it's ultimately the best solution. I was thinking of trying to mess around with it myself, but decided it was a bit beyond my skill levels...basically backup the partition, format in yaffs, then restore the data, right?

stock kernel doesnt not support yaffs2

raspdeep said:
stock kernel doesnt not support yaffs2
Click to expand...
Click to collapse
Yes, you're correct, I was just coming back to edit that out of my post. I forgot I was still running a custom kernel the last time I ran cat /proc/filesystems and that kernel supported yaffs. I'm back on stock JM5 kernel now and see no yaffs support.
original post amended.

ok, you are probably running my kernel.. that kernel is kinda outdated cos the OC div table is not done properly so flash back to stock or my latest oc kernel with wake lag fixed

raspdeep said:
stock kernel doesnt not support yaffs2
Click to expand...
Click to collapse
Yes, but why not make an ultimate fix using your updated kernel? =)

Cyanogenmod 7.x/CM7 Based Roms - Mods a2sd sd-ext Ext4 and Linux-swap Patch2

Update:
YOU MUST have a recovery that supports ext4 in order to use this patch. Currently there is only one recovery for G2 that I know of that is up-to-date that supports ext4 partitioning. That recovery is ext4 recovery. After you get ext4 recovery installed format and wipe everything before installing your rom of choice.
1. Format system
2. Format data
3. Format cache
4. Format sd-ext
----------
A lot of these scripts are based on the stock Cyanogenmod scripts to mount sd-ext partition and allow a2sd.
I've edited the stock system/etc/init.d/05mountsd to mount ext partition as ext4 instead of ext3. The system/etc/init.d/10apps2sd was made by Cyanogen himself and it can be found on the Cyanogenmod github. I've edited it to activate and utilize the sd-ext partition of the device. The swap patches and the cmparts source edits are all my own work. Please see the github for more details.
Required for swap: For swap you need a kernel that supports swap. E.G., Faux123, and may be others but it is your responability to find out which kernels support swap
Udate: this current patch is still working fine for me on the latest nightlies (deodex roms only). But there is a certain way that this patch needs to be installed.
It does not matter if you wipe or do not wipe before flashing.
1. If you are flashing this on cyanogenmod nightlies you need
to flash in this order, otherwise the permissions for your
rom will not be correct. Flash the rom first, then the
patch, then the gapps.
2. For flashing on other CM based roms (deodex only). As
many of you might know, Some roms already include
gapps. So because of this, we will need to flash a
compatible deodex Rom, since the patch sets
permissions for the system, and gapps will not work
correctly with the permissions if already installed in the
system. Flash in the same order you would for normal
cyanogenmod roms. Rom first, then patch, then gapps.
Yes even if the rom already includes
gapps you still must flash gapps.
This thread will only be discussion for Cyanogenmod These are AOSP Roms. DO NOT EVER ASK ABOUT SENSE ROM TWEAKS EVER, they just simply won't work with these mods.
Do not submit revised versions that are already posted, I will try to keep the patches as updated as possible. Do not distribute or modify any of the scripts without my given consent, or at least give me credit!
I am not responsible for you breaking something on your device. If you come and tell me that my mods messed up your phone, I will laugh at you.
I have been running these mods flawlessly with no issues. So let's get right into it.
Options:
WARNING: Before you do anything, do a nandroid
backup. If you need to partition your sdcard via recovery, back up your
entire sdcard to your pc before doing so as it will get formated.
If you want a2sd, then you will need a ext4 partition on your sdcard. I
recommend at least a 1GB+ partition. That's it, the scripts will do the
rest.
You can not have any other types of a2sd installed before applying the patch.
The patch doesn't remove, it installs If you have manually installed some
other type of a2sd, you will need to wipe and re-flash rom. The main
important thing is, make sure system gets wiped.
If you want Linux-swap, just simply add a swap partition to your sdcard when
you go to format it in recovery, simple.
Next download and flash the latest patch over your current rom. Be aware
that if you have a swap partition, that your phone will reboot itself once after
your initial boot. Don't freak out and come crying about how your phone is
boot looping, it only reboots once. This is all part of the initial setup to make
sure swap is working properly.
How to check if a2sd is active and working in terminal emulator from your
phone
Code:
$ su
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 183.6M 32.0K 183.6M 0% /dev
tmpfs 183.6M 0 183.6M 0% /mnt/asec
tmpfs 183.6M 0 183.6M 0% /mnt/obb
/dev/block/mmcblk0p26
487.8M 143.8M 318.9M 31% /system
/dev/block/mmcblk0p27
430.0M 147.3M 260.5M 36% /data
/dev/block/mmcblk0p28
149.6M 47.5M 94.4M 33% /cache
/dev/block/mmcblk0p31
19.9M 17.2M 2.7M 86% /devlog
/dev/block/mmcblk1p2 1.9G 1.0G 788.7M 57% /sd-ext
/dev/block/mmcblk1p2 1.9G 1.0G 788.7M 57% /data/app
/dev/block/mmcblk1p2 1.9G 1.0G 788.7M 57% /data/app-private
/dev/block/mmcblk1p2 1.9G 1.0G 788.7M 57% /data/dalvik-
cache
If you see this part then you are golden
Code:
/dev/block/mmcblk1p2 1.9G 1.0G 788.7M 57% /sd-ext
/dev/block/mmcblk1p2 1.9G 1.0G 788.7M 57% /data/app
/dev/block/mmcblk1p2 1.9G 1.0G 788.7M 57% /data/app-private
/dev/block/mmcblk1p2 1.9G 1.0G 788.7M 57% /data/dalvik-cache
How to check if swap is active working from terminal emulator on your
phone
Code:
$su
# free
total used free shared buffers
Mem: 376008 353776 22232 0 15756
-/+ buffers: 338020 37988
Swap: 249544 36780 212764
Next, enjoy your new mods
CMParts (Cyanogenmod settings source): https://github.com/pbeeler/android_packages_apps_CMParts
Changelog: https://github.com/pbeeler/android_packages_apps_CMParts/commits/gingerbread

Holy crap, its Sparksco. How are you doing bro. Looks good, I really don't use a2sd but other might.
Coming from the DARKSIDE.

Haha good man. Yeah this is only really usefull if you are a really heavy app user. That's why I recommend a 1GB ext partition. I'll also try to keep it updated for cm9 once it comes out. How the heck have you been?
Sent from my PG06100 using xda premium

sparksco said:
Haha good man. Yeah this is only really usefull if you are a really heavy app user. That's why I recommend a 1GB ext partition. I'll also try to keep it updated for cm9 once it comes out. How the heck have you been?
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
I am good, Deving away with this great device. My old team pretty much jump started the dev community for the MT4G about a year ago, we released like 10 Roms, Now we all went are seperate ways and I joined up with TDJ and we are now DARKSIDE Dev Team. I am working on Sense 3.5 Rom, ICS Rom (built from source), and a CM7-Hybrid Rom. Besides that I am hanging in there. Thanks for the Mod. What are you up to?
Edit: Anybody wanting to try this, Do it, I completely support anything Sparksco offers, his Rom was legit back in the day of the G1, He is a great dev. There you go gave you some endorsement. lol

Royalknight6190 said:
I am good, Deving away with this great device. My old team pretty much jump started the dev community for the MT4G about a year ago, we released like 10 Roms, Now we all went are seperate ways and I joined up with TDJ and we are now DARKSIDE Dev Team. I am working on Sense 3.5 Rom, ICS Rom (built from source), and a CM7-Hybrid Rom. Besides that I am hanging in there. Thanks for the Mod. What are you up to?
Edit: Anybody wanting to try this, Do it, I completely support anything Sparksco offers, his Rom was legit back in the day of the G1, He is a great dev. There you go gave you some endorsement. lol
Click to expand...
Click to collapse
Very nice. Glad to see your doing well with the deving. I'm accually just been making kernels most of the time, but these patches are my little side projects when I have time. Thanks for the endorsement. Still just tinkering around here and there, but have been using github and working with source code a lot more now.
Sent from my PG06100 using xda premium

Damn I seen Sparksco name and got really happy. I miss your rom

sparksco said:
Very nice. Glad to see your doing well with the deving. I'm accually just been making kernels most of the time, but these patches are my little side projects when I have time. Thanks for the endorsement. Still just tinkering around here and there, but have been using github and working with source code a lot more now.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
If you want to drop some kernels on this forum no one would object. We already have some great ones to choose from but nothing wrong with more choices. I'll test! Lol.
Sent from my HTC Glacier using XDA App

Hell yeah! I used your roms all the time on the g1. Good to see you around!
Sent from my HTC Glacier using XDA App

estallings15 said:
If you want to drop some kernels on this forum no one would object. We already have some great ones to choose from but nothing wrong with more choices. I'll test! Lol.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Now that you mention it I did try to build a kernel for glacier based on my own kernel but it did not work out very well. Hopefully more kernels will start to pop up once cm9 is available that support swap. The best way to tell if it's working is on the logcats
Sent from my PG06100 using xda premium

Thanks man, I have been waiting for more mods like this. Don't know why devs haven't been incorporating this into all their roms. Appreciate the work, looking forward to seeing u more around here.

They could if they want to. The partitions are not required to be used in roms, so it makes it very usefull.
Sent from my PG06100 using xda premium

Updated OP with recovery instructions. Ext4 recovery should work great for using this patch. Anyone else having the audio issue? Tiamat kernel should work for swap unless there's another better kernel that supports swap that I am not aware of.
Sent from my PG06100 using xda premium

Has anyone tried Faux123's kernels on this to see if swap works?
Sent from my PG06100 using xda premium

Alright this is now on rom manager. I made it easier to intall on rom manager but I can't read the comments on there so please post all or any questions here instead of on rom manager.
Sent from my PG06100 using xda premium

[Q] Cross flashable to Samsung Rugby Smart?

Hi everyone, I was wondering if any DEVs here could check if the Samsung Rugby Smart i847 source code is compatible with any of the Galaxy W development. I have no experience with compiling and understanding kernels but I do know that both phones should have the same chipset with the exception of the modem and possibly the camera or screen. The partitions are very similar with the exception of two partitions.

I guess not. because having different partitions could mean a lot. Also device drivers are all device specific. Should you try to flash.. say.. stock rom, you might experience bootloops or possibly bricking your phone

The risk of softbrick is large. I've read somewhere on the forum that the hardware on the Xperia Arc was the same of our phone, just the processor clock is lower. SO I decided to flash a ROM and got a hard softbrick that I've took some hours to revert.

Interestingly, the CPU hardware is labeled as I8150. I assume that Samsung took the Galaxy W and slapped some better hardware on top of it .(AMOLED screen instead of TFT) For the modem, I'm unsure if it's the same or different because I noticed on some settings that the WCDMA band were 850, 900, 1900, 2100.
The similar partitions are
# cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5632 mmcblk0p8 //boot
179 9 6488 mmcblk0p9
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 547840 mmcblk0p15 //system
179 16 204800 mmcblk0p16 //cache
179 17 1136640 mmcblk0p17 //data
179 18 500 mmcblk0p18 //preload <-- this is the only difference besides the sdcard (51200 instead of 500)
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27 //efs
179 28 1693696 mmcblk0p28 //sdcard
Click to expand...
Click to collapse
The only difference would most likely be the screen and possibly modem to allow porting from the galaxy w which shouldn't be too complicated from the source code given by Samsung.

Almost works!
wathou6 said:
The only difference would most likely be the screen and possibly modem to allow porting from the galaxy w which shouldn't be too complicated from the source code given by Samsung.
Click to expand...
Click to collapse
I have a Rugby. I went ahead (crazy me) and flashed CM9 Alpha 4 on it. Only one minor problem: no screen display! Totally blank! The screen hardware is fine because I can see it works during fastboot, but Clockwork Mod and CM9 don't display anything.
Anything I could do to help the developers, let me know!

Toughdroid said:
I have a Rugby. I went ahead (crazy me) and flashed CM9 Alpha 4 on it. Only one minor problem: no screen display! Totally blank! The screen hardware is fine because I can see it works during fastboot, but Clockwork Mod and CM9 don't display anything.
Anything I could do to help the developers, let me know!
Click to expand...
Click to collapse
You are crazy! Here's a working Clockwork Mod if you can use adb http://rootzwiki.com/topic/27265-recovery-cwmr-5504-for-samsung-sghi847-rugby-smart/
The screen display don't showing up is a kernel issue since the Rugby uses a different screen (AMOLED). I don't really have a backup for you to restore to though.

wathou6 said:
You are crazy!
Click to expand...
Click to collapse
Apparently I am. I have now hard-bricked my Rugby.
wathou6 said:
Here's a working Clockwork Mod if you can use adb
Click to expand...
Click to collapse
That is cool. Unfortunately I tried to install it like this:
dd if=recovery.img of=/dev/block/mmcblk0p13
It copied into the partition, now the device won't do anything. I'm sure I copied it into the wrong partition. Any ideas how to recover from this point? I can't even get into fastboot now.

Galaxy W i8150 config.gz
Toughdroid said:
I have a Rugby. I went ahead (crazy me) and flashed CM9 Alpha 4 on it. Only one minor problem: no screen display! Totally blank! The screen hardware is fine because I can see it works during fastboot, but Clockwork Mod and CM9 don't display anything.
Anything I could do to help the developers, let me know!
Click to expand...
Click to collapse
Could someone please post their /proc/config.gz file from the Galaxy W i8150? I want to take a look at the differences between the kernels to try to figure out why the screen doesn't show anything on the Rugby Smart.

hope this helps
https://dl.dropbox.com/u/485128/config.gz
(i tried to copy/paste the text but it was too long. so there you go

Ekril said:
https://dl.dropbox.com/u/485128/config.gz
(i tried to copy/paste the text but it was too long. so there you go
Click to expand...
Click to collapse
Thanks man. I just looked at the diff between the two, and there are only a handful of differences. Hopefully I can get this sorted out. I am new to Android development, but have been compiling Linux kernels for ~15 years of so now :good:

anything else i can do?

I am a total noob with android development, but i have a i847 Rugby Smart coming, got it on ebay for 210 $, i will document myself and start android developing because, it seems, this device has close to none support at all, despite the fact that it ws released in march, i might be able to get the stock rom from AT&T too. Being a dedicated AT&T phone i doubt they will release any update soon, so we must do with what we have.

pkkilleru said:
I am a total noob with android development, but i have a i847 Rugby Smart coming, got it on ebay for 210 $, i will document myself and start android developing because, it seems, this device has close to none support at all, despite the fact that it ws released in march, i might be able to get the stock rom from AT&T too. Being a dedicated AT&T phone i doubt they will release any update soon, so we must do with what we have.
Click to expand...
Click to collapse
Any progress on this? I myself have a Rugby Smart and would love to see any firmware updates. I'll even volunteer it to testing.
I also have a good amount of excess cpu / ram / storage if you need help with any builds.

Count me in on this, I plan on getting one and would like to see something other than stock on it.
Sent from my SGH-I897 using xda app-developers app

kemonine96 said:
Any progress on this? I myself have a Rugby Smart and would love to see any firmware updates. I'll even volunteer it to testing.
I also have a good amount of excess cpu / ram / storage if you need help with any builds.
Click to expand...
Click to collapse
I've tried arco's Galaxy W rom many different ways. Tried it just as he packaged it, but w/ the Rugby Smart kernel. And I did several different combinations of arco's rom w/ various libs/firmwares/binaries from the Rugby Smart added in. Unfortunately I have not been able to get anything to boot successfully.
I am still going to keep trying - this has been a good learning process for me, as I have ~15 years experience w/ Linux but never dabbled in Android. If anyone has any tips or can help out, speak up!

nicedream06 said:
I've tried arco's Galaxy W rom many different ways. Tried it just as he packaged it, but w/ the Rugby Smart kernel. And I did several different combinations of arco's rom w/ various libs/firmwares/binaries from the Rugby Smart added in. Unfortunately I have not been able to get anything to boot successfully.
I am still going to keep trying - this has been a good learning process for me, as I have ~15 years experience w/ Linux but never dabbled in Android. If anyone has any tips or can help out, speak up!
Click to expand...
Click to collapse
I read on the Cyanogen forums that the display is different on the Rugby Smart than the normal Galaxy W variants, have you tried changing any kernel options in the Galaxy W variant sources?
I have a stock device currently and if you need anything from proc / sys / wherever I can pass along, just let me know.
Also, if you have any instructions on generating an ODIN image, I may be able to put something together for flashing back to stock.

kemonine96 said:
I read on the Cyanogen forums that the display is different on the Rugby Smart than the normal Galaxy W variants, have you tried changing any kernel options in the Galaxy W variant sources?
I have a stock device currently and if you need anything from proc / sys / wherever I can pass along, just let me know.
Also, if you have any instructions on generating an ODIN image, I may be able to put something together for flashing back to stock.
Click to expand...
Click to collapse
I haven't tried changing any of the kernel options in arco's cyanagen build, but based on the config.gz files from the stock kernels in both of these devices there are very few differences. Here is the output when I diff the two files:
Code:
diff config-i8150 config-i847
4c4
< # Sat Apr 14 09:38:45 2012
---
> # Sat Jan 28 15:23:37 2012
271,272c271,272
< CONFIG_MACH_ANCORA=y
< # CONFIG_MACH_APACHE is not set
---
> # CONFIG_MACH_ANCORA is not set
> CONFIG_MACH_APACHE=y
274a275,277
> CONFIG_HW_REV_USING_SMB328=0
> CONFIG_MICROUSB_DEBUG=y
> CONFIG_BATT_MICROVOLT_UNIT=y
387c390
< # CONFIG_VP_A2220 is not set
---
> CONFIG_VP_A2220=y
1046c1049
< CONFIG_SAMSUNG_FM_SI4709=y
---
> # CONFIG_SAMSUNG_FM_SI4709 is not set
1047a1051
> # CONFIG_AUTO_INPUT_EVENT_GENERATOR is not set
1232c1236
< # CONFIG_INPUT_SECBRIDGE is not set
---
> CONFIG_INPUT_SECBRIDGE=y
1277c1281
< # CONFIG_TOUCHSCREEN_MXT224 is not set
---
> CONFIG_TOUCHSCREEN_MXT224=y
1289,1290c1293
< CONFIG_TOUCHSCREEN_MELFAS_MCS8000=y
< CONFIG_TOUCHSCREEN_MELFAS_FIRMWARE_UPDATE=y
---
> # CONFIG_TOUCHSCREEN_MELFAS_MCS8000 is not set
1314c1317
< # CONFIG_GYRO_K3G is not set
---
> CONFIG_GYRO_K3G=y
1379c1382
< # CONFIG_DCC_TTY is not set
---
> CONFIG_DCC_TTY=y
1500c1503
< CONFIG_BATTERY_ANCORA=y
---
> CONFIG_BATTERY_APACHE=y
1760,1761c1763,1764
< # CONFIG_QUP_EXCLUSIVE_TO_CAMERA is not set
< CONFIG_SENSOR_SR030PC30=y
---
> CONFIG_QUP_EXCLUSIVE_TO_CAMERA=y
> # CONFIG_SENSOR_SR030PC30 is not set
1763c1766
< # CONFIG_SENSOR_SR130PC10 is not set
---
> CONFIG_SENSOR_SR130PC10=y
1837c1840
< # CONFIG_FB_MSM_LCDC_S6E63M0_WVGA is not set
---
> CONFIG_FB_MSM_LCDC_S6E63M0_WVGA=y
1839c1842
< CONFIG_FB_MSM_LCDC_SAMSUNG_ANCORA=y
---
> # CONFIG_FB_MSM_LCDC_SAMSUNG_ANCORA is not set
1863c1866
< # CONFIG_FB_MSM_LCDC_S6E63M0_WVGA_PANEL is not set
---
> CONFIG_FB_MSM_LCDC_S6E63M0_WVGA_PANEL=y
1865c1868
< CONFIG_FB_MSM_LCDC_SAMSUNG_ANCORA_PANEL=y
---
> # CONFIG_FB_MSM_LCDC_SAMSUNG_ANCORA_PANEL is not set
2218c2221
< CONFIG_MMC_MSM_CARD_HW_DETECTION=y
---
> # CONFIG_MMC_MSM_CARD_HW_DETECTION is not set
2221d2223
< CONFIG_MMC_MSM_SDC1_DUMMY52_REQUIRED=y
2224d2225
< CONFIG_MMC_MSM_SDC2_DUMMY52_REQUIRED=y
2228d2228
< # CONFIG_MMC_MSM_SDC4_DUMMY52_REQUIRED is not set
2230c2230
< # CONFIG_MMC_MSM_PROG_DONE_SCAN is not set
---
> CONFIG_MMC_MSM_PROG_DONE_SCAN=y
2685c2685
< CONFIG_CRYPTO_RNG=y
---
> CONFIG_CRYPTO_RNG=m
2771c2771
< CONFIG_CRYPTO_ANSI_CPRNG=y
---
> CONFIG_CRYPTO_ANSI_CPRNG=m
2773,2775c2773,2775
< CONFIG_CRYPTO_DEV_QCRYPTO=y
< CONFIG_CRYPTO_DEV_QCE=y
< CONFIG_CRYPTO_DEV_QCEDEV=y
---
> CONFIG_CRYPTO_DEV_QCRYPTO=m
> CONFIG_CRYPTO_DEV_QCE=m
> CONFIG_CRYPTO_DEV_QCEDEV=m
You can see that there are a few FB options that are obvious differences, which is probably related to the different displays. I haven't had any luck getting it to work though.
Oh and my device is stock now. Well, it's the stock ROM, rooted and with all the bloatware removed. But I am able to query the /proc and /sys directories on my device.

nicedream06 said:
I haven't tried changing any of the kernel options in arco's cyanagen build, but based on the config.gz files from the stock kernels in both of these devices there are very few differences. Here is the output when I diff the two files:
You can see that there are a few FB options that are obvious differences, which is probably related to the different displays. I haven't had any luck getting it to work though.
Click to expand...
Click to collapse
From what I see in the diff you posted, I'd try using the config from the Rugby Smart in conjunction with the rest of arco's build and see what happens. To me it looks like the display options are the key differences to getting his kernel working with our device.

kemonine96 said:
From what I see in the diff you posted, I'd try using the config from the Rugby Smart in conjunction with the rest of arco's build and see what happens. To me it looks like the display options are the key differences to getting his kernel working with our device.
Click to expand...
Click to collapse
I'm going to give that a try when I get a chance, but I have a question about building the kernel from arco's source.
His github repository doesn't have a .config file for building his kernel - so how can I build it with the options he uses for his ROM? I know you can extract the config.gz from a running kernel but I don't have that. If I run make menuconfig, will it automatically get the correct options from the various Kconfig files in the source tree?

nicedream06 said:
I'm going to give that a try when I get a chance, but I have a question about building the kernel from arco's source.
His github repository doesn't have a .config file for building his kernel - so how can I build it with the options he uses for his ROM? I know you can extract the config.gz from a running kernel but I don't have that. If I run make menuconfig, will it automatically get the correct options from the various Kconfig files in the source tree?
Click to expand...
Click to collapse
I do not know offhand, I've never tried to build a version of CM before. I was going to investigate the build process in the coming days, see if I can get my environment setup and ready to go for testing.
I am curious though: how were you able to recover after flashing arco's build back to a working device?

Android L for Galaxy W? In Custom way?

Oh,,, hell yeah, i want it badly. :victory:

+1

No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.

SGWUser said:
No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.
Click to expand...
Click to collapse
Maybe sir arco will save us again when the sources are released You never know..

a port may come soon but we have to wait until it is final so they release cm 12

eri000 said:
a port may come soon but we have to wait until it is final so they release cm 12
Click to expand...
Click to collapse
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version

dqsnunes said:
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version
Click to expand...
Click to collapse
the CM team announced that there will be NO CM version until the google releases the final image of android L on AOSP.This doesn't mean we will have a final stable version of cm immediately BUT we will only see a cm12 build when final android L gets merged into aosp.
^That is for other phones that get CM OFFICIAL.For ancora we have to wait a little bit more for unofficial cm, which is based on official cm.So no official--- no unofficial (arco if he has time to mess with it,or others)

BTW, Android L is currently being ported to the Nexus 4 and Nexus 7 2012 right now. Both are almost functional.

I think even if we were to have Android L here, i don't think it will be responsive. Google said, Animation transitions run at 60fps, Im not sure if overall perfomance can run at the same fps because i bet our processor is not powerful enuff or smth. CMIIW.

Android L Port For Nexus 4
Newest Android L Port For Nexus 4 Is Now Fully Operational And Ready For Download
INFO

I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:

theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
A swap partition for art can't help?

theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards

sir mordred said:
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
Click to expand...
Click to collapse
Nice thinking and good luck :good:

sir mordred said:
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
Click to expand...
Click to collapse
Umm very interesting if you want some testers,i'm here.

If you have cm11 theme chooser:
http://forum.xda-developers.com/android/themes/theme-l-ready-t2802979
https://play.google.com/store/apps/details?id=nexbit.icons.moonshine
Settings>Performance>Force high-end graphics>check
AND YOU HAVE L IN YOUR WONDER(I LOVE MY WONDER)

what is android L? can someone tell me about it please?

smartiescoke said:
what is android L? can someone tell me about it please?
Click to expand...
Click to collapse
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).

arsradu said:
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).
Click to expand...
Click to collapse
whoa! really? awesome! i always been waiting google to update different kind of android version. ui and etc, hope it will come to our wonder soon! XD

oh man i love android L ui and statusbar. Hoping our Great Developer can bring this to our Wonder.
#sorry for my bad english.

YU5510A P3 Hardware Variant - Discuss

This is the yureka plus model ordered from snapdeal. Box mfg date is aug 2016. It comes with stock lollipop and VoLTE enabled out of the box.
Hardware sticker behind the battery says P3
Here is the partition size as per adb:
adb devices
adb shell
cat /proc/partitions
[email protected]:/ # cat /proc/partitions
major minor #blocks name
0 15392768 mmcblk0
1 1 mmcblk0p1
2 8 mmcblk0p2
3 512 mmcblk0p3
4 512 mmcblk0p4
5 512 mmcblk0p5
6 512 mmcblk0p6
7 512 mmcblk0p7
8 512 mmcblk0p8
9 512 mmcblk0p9
10 512 mmcblk0p10
11 1024 mmcblk0p11
12 20480 mmcblk0p12
13 1536 mmcblk0p13
14 1536 mmcblk0p14
15 262144 mmcblk0p15
16 32768 mmcblk0p16
17 1024 mmcblk0p17
18 512 mmcblk0p18
19 512 mmcblk0p19
20 131072 mmcblk0p20
21 1024 mmcblk0p21
22 32 mmcblk0p22
23 1536 mmcblk0p23
24 16 mmcblk0p24
25 4096 mmcblk0p25
26 4096 mmcblk0p26
27 32768 mmcblk0p27
28 32768 mmcblk0p28
29 2621440 mmcblk0p29
30 65536 mmcblk0p30
31 12148719 mmcblk0p31
32 4096 mmcblk0rpmb
Today I went to the service centre to have them change the OS to cyanogenmod but after waiting for two hours, the guy came out of his cabin and showed me the P3 sticker and said it was non compatible with cyanogenmod. He said this device didn't have fastboot mode and instead something else was present in the volume up config.
Around half of the people in this service centre had brought their yureka plus to the store because it was getting too hot and battery wasn't lasting through the day. One particular guy brought his yureka plus with burned display. According to him, the camera app and flash had started up automatically while it was in his pocket turning it hot and by the time he realized something warm in his pocket, parts of display pixels had already gone dead black.
Those yureka users who had come for battery issues were sent back saying it was a faulty battery issue - change battery. Some users had bought it from flipkart and were unable to replace it. I bought mine from snapdeal last week and as I was filing a return request on the website, I found that it was only eligible for a "replacement" policy.
About a month or two ago, I had wondered why so many people were selling their 2-6 month old yureka plus on olx and now I know the reason. The YU company has put a faulty device on sale and too many people have ended up buying it after watching some youtube review videos(although sharmaji technical had clearly instructed "just don't buy yureka plus" which I ignored) when they should have read the forums for genuine issues.
The new P3 device is pending:
1) rooting
(achieved !! see next post)
2) replacing kernel to solve battery and heating issue
(Partly achieved using root and bypassing kernel through apps)
3) custom rom to a) fix lagging issues and b) many features which are considered basic on 2016 absent in this stock rom
Kindly post more info on P3 in this thread to help us understand the issue.

UPDATE:
I have managed to root this device. I did this using the PC version of kingoroot. Kinguser did not work on my phone as you guys suggested and I also tried different versions of kinguser but failed.
Steps to root P3:
1) Download kingoroot PC software from their official site and complete installation
2) On phone > Enable developer mode > Turn on USB debugging
3) Start kingoroot on PC > Connect phone to pc
4) Disable your anti-virus for 15 mins (this is very important; else you won't achieve root)
5) Follow kingoroot instructions and click next when asked > it will download some very nasty exploit scripts which anti-virus don't like.
6) It will finally show root achieved
Now, on phone remove both kingoroot apps(kingoroot and its version of superuser). And install superSU from play store.
Now, download link2sd app from play store and delete many useless Google apps from /system partition.
STEPS TO CONTROL BATTERY DRAIN AND HEATING ISSUES:
This phone comes with a faulty stock kernel which controls the CPU speed. After gaining root, download kernel adiutor from play store. The stock kernel has the minimum frequency set at 960mhz by default. So it runs above 960mhz even at idle mode.
Hence, the reason for drain and hot phone.
Using kernel adiutor, change minimum frequency to 200mhz for both big and small set of 4 CPUs. In the max side, set it to 800mhz in both sets - yes, we are under clocking this chip as 615 chip gets too hot if run constantly above 1ghz. Set the governor to ondemand option. And enable on boot option so that it can set these settings every time phone boots. Also hide notifications if you want.
Now, download DS battery saver from play store. The stock kernel is stupid so it won't send your phone to deep sleep and kernel adiutor won't either. But DS will send phone to deep sleep as soon as you hit sleep button.

hi if u want Yureka full working with p1 version software .in exchange of Yureka plus p3 then u can contact me .[