yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Q&A, Help & Troubleshooting] mailppl:
Hi Ashwin,

Can I flash a different country's ROM on my tab 7.7 (saudi / middle east) as ICS is officially still not available for the middle east. Are the firmwares available on sammobile & samsung-updates dot com genuine and risk free ? If yes, then how do I flash it on the tablet.

Sorry for the questions, still a newbie :)

Regards,

Kaustav
[Samsung Galaxy Nexus] josip-k:
hey guys.i installed back oficcial stock jelly bean rom now,and my camera isnt working,it just force closes.is there any fix?id be very grateful,thanks :)
[Samsung Galaxy Nexus] Petrovski80:
Did you upgrade from 4.0.4 stock? And by stock, do you mean flashing the Google factory images for your device?
[Samsung Galaxy Nexus] josip-k:
Odin flashed stock ics the ota upgrade to jb
[Samsung Galaxy Nexus] Petrovski80:
I just saw a thread where a guy had FCs for camera/gallery after flashing a custom ROM. By the looks of his logcat, the drivers for the camera got messed up somehow so Android can't start it. Could that be your issue as well?
[Samsung Galaxy Nexus] josip-k:
May be. Dont really know
[Samsung Galaxy Nexus] josip-k:
Solved with franco kernel :D thanks for the help,and thanks Francisco! :))
[Samsung Galaxy Nexus] Petrovski80:
Interesting. Glad you fixed it.
[HTC One X] DharmzVala:
Hey all,

Since I still have ages till I go back to university I was thinking of starting to make my own custom roms to share with the xda community as a part time thing. But what I wanted to know is what are the requirements for this, do you need to have good skills in software programming or can anyone make their own roms with little or no experience in programming at all. As for me I do have some knowledge and experience in Java and C as it was part of my degree for the first two years but i wouldn't say i'm an expert just good enough i guess lol. So is there like a guide or something out there which would help newbies like me to get on the right path of making custom roms. I dont want to start off big just something basic like a rom that has smooth performance and good battery life and once i get the jist of things i'll step it up a level and allow the user to tweak their rom like the viper roms and what not and just build it up from there.

Many thanks.
[HTC One X] treebill:
XDA had a news update on just this topic!

http://www.xda-developers.com/android/would-you-like-to-learn-how-to-develop-on-android/
[HTC One X] DharmzVala:
Thanks I shall check it out!
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
History

JackpotClavin first got a 3.x kernel working on the SGP5.0. He used this kernel and a modified Captivate firmware to release a CM10 "preview." Since then, he has done some work on fixing kernel issues, and I worked on trying to fix some things in Android, releasing a "pre-alpha." However, we were limited by the fact it was ported, not built. It took quite a while, but I finally figured out the Android build system and created a device tree. Well, as of 21 November, it has matured enough to create a zip that installs and boots cleanly, and so has entered the "alpha" stage. On November 27, a functional CWM was attained, and on November 28, internal storage was fixed. Then we decided to use the 2.6.35.7 stock-based kernel with back-ported drivers. After a month of off and on work, it booted usably. Things like vibration and button lights were easy to fix, but wi-fi drivers were a headache. So I decided to, for now, use the old and slow ones, because at least they work. A lot of work was done the last week of December, and by New Year's Day, the only things left broken were audio, Bluetooth, and the camera. Well, come to find out Galaxy Tab audio and camera HAL work on our device. So by the end of the day, I had gotten to what I consider a beta.

Going Forward

Now that the beta is out, this thread is for development discussion only.

Eventually, we will probably go back to the 3.0 kernel, but not for a while.

local_manifest.xml for CM10

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Mevordel/android_device_samsung_venturi" path="device/samsung/venturi" remote="github" revision="jellybean" />
<project name="Mevordel/android_kernel_samsung_venturi" path="kernel/samsung/venturi" remote="github" revision="jellybean" />
<project name="Mevordel/android_system_vold" path="system/vold" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
</manifest>

Other Git Links

3.0 Kernel source: https://github.com/Mevordel/android_kernel_samsung_venturi_3.0

Initramfs for 3.0 kernel: https://github.com/Mevordel/venturi_cm10_initramfs
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Download

The beta is out. Use it. These are for historical / testing / file-yanking purposes only.

Alpha 7: http://www.mediafire.com/?3ji7u4ifx53v4vy - fixes rotation, almost fixes storage (both), enable int'l home button & software buttons, fixes gps

Alpha 6: http://www.mediafire.com/?yasfuv630v743gr - fixes wi-fi (old drivers), external storage, vibration, button lights

Alpha 5: http://www.mediafire.com/?9u1dhu8qlz6euy4 - first with kernel 2.6.35

Alpha 4: http://www.mediafire.com/?c36chfcrsde7s6s - added storage

Alpha 3: http://www.mediafire.com/?c8o33cjb19rw8zf - added CWM

Alpha 2: http://www.mediafire.com/?9nkguo3y62dwyxl - added WiFi

Alpha 1: http://www.mediafire.com/?nuou91atn1x03tw - built from source

Pre-Alpha: http://www.mediafire.com/?xfaiw6i57cqdexf - captivatemtd port

Workarounds (must be applied each boot)

To enable GPS (Alpha 6 and earlier)

Run as root:

gpsd -d /vendor/etc/gps.xml

To trick vold and mount internal storage (Alpha 3 and earlier)

Run as root:

rm "/dev/block/vold/179:8"
mknod "/dev/block/vold/179:8" b 259 9

Then run 'vold' or go to Settings -> Storage and click "Mount."
[Samsung Galaxy Player 4.0, 5.0] Cm9aphla:
good now you and jackpot clavin are working on a 3.x kernel
[Samsung Galaxy Player 4.0, 5.0] gmillz:
It would he great if we could get a 3.4 kernel. It would make everything easier
[Samsung Galaxy Player 4.0, 5.0] spartacus279:
Looks great, is there any way I could help with patching the 3.0xx kernel?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
The way I'm doing it now is through the kernel.org incremental patches. So going to 3.4 would just mean a few more patches.

Sure. I posted what I'm doing at the top of the 2nd post. I'm working my way down. If you or someone else wanted to start somewhere else in the list then just reply so I know, and send me the files you've edited when you're done.

Just in case, to explain what I'm doing, I'm trying to edit the listed files so they do not cause conflicts when I apply the mentioned patch. So what I'm doing is attempting to patch, looking at the "rejects file," and noting what the file is "supposed" to look like before patching - that is, before the "+" lines are added and the "-" lines are removed. The reason the patches fail is because the file doesn't look like that. So I'm editing the files in the appropriate places so that they do match up.

If you don't understand, feel free to ask questions, and if you still don't think you can help, that's OK too. Not everyone is cut out to be a kernel dev :)
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
How do you patch? This could be interesting for the 4.0 users :D.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
In addition to releasing a source tarball for each kernel release, kernel.org also releases patches (at the bottom) that will upgrade your sources from the previous release (to conserve bandwidth, etc.). I'm using those patches, but most of the work is cleaning up where Samsung and mainline both modified files.
[Samsung Galaxy Player 4.0, 5.0] john9:
great share!Thanks for your work!
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
the patches are the .sign files right?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
No, they are the patch - somenumber .bz2 or .xz, for example patch-2.6.12.xz

I just realized that the main kernel.org no longer keeps minor patches for that old of a release, so you'll have to look on a mirror.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Are you sure this will work? I claim no knowledge whatsoever of kernels, but Oisis has been trying to boot a 3.0x kernel for the 4.0, and he's still missing these files:

CONFIG_VIBETONZ - drivers/misc/Kconfig:481 - missing in 3 - to do

CONFIG_TOUCHSCREEN_QT602240 - drivers/input/touchscreen/Kconfig:624 - missing 3 - to do

CONFIG_VIDEO_ISX005 - drivers/media/video/Kconfig:1142 - missing in 3 - to do

CONFIG_SENSORS_MMC31XX - drivers/misc/Kconfig:341 - missing in 3 - to do

INPUT_BMA222 - drivers/input/misc/Kconfig:55 - missing in 3 - to do

Perhaps you guys have them, perhaps not, but i'm just throwing that out there :).

EDIT: Now I seem like an idiot for not fully reading the OP :D. It looks like you guys are missing many of the same files we are, but fortunately we only have these left to patch.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I'm not sure what you mean by missing... All of the files are there in Samsung's stock kernel source, they just aren't the 3.x versions (if those exist).

Attached is some of those files, taken from my current working tree.
[Samsung Galaxy Player 4.0, 5.0] Neodymium:
QT602240 Is not needed. It is already included in kernel named xt2240. And all the files you have listed is the differences between galaxy s and galaxy player
[Samsung Galaxy Player 4.0, 5.0] theraf:
surely you can just pull these files from the samsung opensource website
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
How do you build kernels? I would help but don't know too much about it. I can learn easily though
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Yeah but the qt and mxt drivers are for the same touchscreen which the the MXTxxx (I don't remember the model).
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
First, it requires a working Linux environment. When you download the source code, some pointers are in the README_Kernel.txt file, and Entropy512 created a nice helper script, called build-linux-yp-g70usa. I'd look there first. Also useful is the "configuring the kernel" section in the main readme.

In short:

1. download toolchain (listed in Readme_kernel), kernel source (from Entropy's or my github or samsung opensource [see OP]) and initramfs source (from Entropy512's github).

2. edit Makefile (search for "cross_compile") to point to toolchain.

3. open a terminal in kernel folder

4. type ./build-linux-yp-g70usa

5. if it all works, you'll have a heimdall/odin-flashable zImage in arch/arm/boot/
[Samsung Galaxy Player 4.0, 5.0] omaroe666:
i was thinking guys ? is the flashlight working ? like the camera is now letting the device hot reboot if you open it but can you use the flash ? im not asking for eta's i was just thinking if the flashlight would work ?
[Samsung Galaxy Player 4.0, 5.0] Neodymium:
I didn't see the GB70 source but maybe it would be same as the method used to GB1-just change camera source
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
Any hope off progres with this ..has anuone work ..to hope or not :D
[Samsung Galaxy Player 4.0, 5.0] james59802:
Dude, you are asking for a verbal smack down. Never ask for status updates
[Samsung Galaxy Player 4.0, 5.0] gskillivenom:
Why ? Dont ask ETA's is the rule. Im pretty sure just wondering that the status is , isnt that bad.
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
Status update requests are equally annoying! Are you developing or contributing to the cause?

Developing kernels and ROMs is perplexing work, even for skilled developers, and they don't need the added stress from people asking for progress updates or ETAs; especially when you have not contributed to the development in anyway.

Just wait like everyone else, or send a PM. Don't clutter the thread with your selfishness. Everyone else is wondering, too. If you don't want to or can't wait, then get a new device or kindly wait until progress is announced.
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
I don't think he was asking for an eta, I think he was just asking if people were still working on it since the thread has been dead for a few days

Sparx639
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
I dont ask for ETA just ask is anyone working on SGP 5 or not because all threads are dead for long time.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I got my player back yesterday and resumed work on it. However, I had oral surgery in the morning and couldn't focus very well. :)
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
Thanks..just dont brick it anymore :D
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Progress update: Today I got a build to boot all the way the first time without messing with it, but I haven't figured out why the kernel isn't flashing properly.

Here is the zip: http://www.mediafire.com/?fz9b96nle8ayiw4

And the kernel: http://www.mediafire.com/?u62iipsho6c0e25

Wifi, Storage, BT, GPS broken. Gapps not included (flash in GB CWM after this zip).

I have to say this is about the end of my ability - I have basically no idea how to fix the other issues. So it may be the last zip until someone else smarter figures some of this out.
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
So are all four broken or just GPS?
[Samsung Galaxy Player 4.0, 5.0] suyash1:
I believe all four are broken
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
That is correct
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
Is camera working?
[Samsung Galaxy Player 4.0, 5.0] suyash1:
It doesn't work and even if it did storage doesn't work so it would be pointless.
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
It'll all end up being fixed eventually just be patient. Also whatever happened to entropy? I thought he did some work with the galaxy players

Sparx639
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Bricked it to the point of no JTAG..
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
Wow how would something like that happen? Like is there a specific thing in the device that causes it?

Sparx639
[Samsung Galaxy Player 4.0, 5.0] hanjosep:
Idk, but considering he made a kernel for the gp5 he probably did something risky
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
Is sound working?
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
I thought Jackpot did the kernel 3.0 for the SGP 5...

I may be wrong though...
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
He did, we were talking about someone else
[Samsung Galaxy Player 4.0, 5.0] :
The download link is invalid. I REALLY wanna try 4.1, so plz fix!
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
You'll get kinda tired with it since the sound and videos are messed up, I kinda just moved back to CM9 because it just really isn't worth it. I need to thank Mevordel, JackpotClavin, and all the others who helped out on this but development is kinda over for right now so I just gave up.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Try prealpha 1 with the kernel from a couple pages ago. The installer for #2 was broken anyways.
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
Is this based off stock or CM10?
[Samsung Galaxy Player 4.0, 5.0] suyash1:
CM10
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
I 2 have give up and back to Chip Rom..ADW launcher had a incredible update and now is fast as f1 car and on GB..ics animation on my player are now faster then on nexus 7 stock launcher ..add some simple memory tweaks,swapit expander for swap and overclock it to 1.5 ghz and i am happy again with player with out CM..
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
We can't give up, can't we ask trinity or Franco for help since they have plenty of experience with kernel Dev on the galaxy nexus? I'm not expecting anything but it wouldn't hurt to ask as they are both pretty cool guys

Sparx639
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Tried asking Franco, never PMed me back. I think I am done with my Player anyways..
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
he is doing 3 kernels in same time so i would do the same if i was in his place
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
I asked the poster of the trinity kernel, if not I am going to look somewhere else. I will take over this if I have to although I do not know anything about the structure of a kernel so far, I can learn very quickly.
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
I'll try and work on the kernel as well, but the one thing I don't understand is how the wifi worked in the Pre-alpha 2 ROM, and not in the newer ZIPs that Mevordel created. Is this due to the kernel, or something with libs?
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
me 2 cant understand..can just libs and wifi files from aplha 2 rom copied to new mevordel Zip
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
Well he changed something and when people say Google is our friend, they mean it. I'm pretty sure we can solve almost anything that a log cat or other error message of sorts throws at us just by searching it

Sparx639
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
I changed the kernel source a few weeks back and renamed the device "Venturi"

The init scripts .rc files had to be changed from init.smdk210.rc or something like that to init.venturi.rc. I know the wifi and pvrsrvinit is on the init.device_name.rc, so perhaps the device is skipping over the init.smdk210.rc because the kernel says the device name is Venturi, not smdk210 anymore, so the init script has to be renamed.

---------- Post added at 10:55 PM ---------- Previous post was at 10:50 PM ----------

Just to clarify what I mean, on the working kernel that is missing wifi, run a cat /proc/cpuinfo and see what the device's name is listed as. If it is named venturi, you will have to renamed the init.smdk210-or-whatever.rc to init.venturi.rc. This will have to be done in the build environment of the kernel and rebuilt with the renamed init scripts
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Are you still working on the Galaxy Player Jackpot?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Hmmm... I'm almost certain which files it chooses is decided by ro.product.device (or whatever the build.prop line is). That's why changing aries to anything else in the prealpha build.prop prevented it from booting. The kernel in prealpha 2 and the new builds is exactly the same, so any new issues are all due to library/binary problems.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
I think the actual /init uses the hardware listed under /proc/cpuinfo. The system isn't even mounted when this file is executed so it can in no way parse the build.prop

And I'll try to get around to it next week around thanksgiving. Has anything changed since were I left off a few weeks back?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
How have you changed the kernel to rename it venturi? I would like to name my device board palladio (as it's in the configuration.)
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
Ok, thank you for this info. I will see if I can rename the scripts and re-build the kernel. Also what is causing the sound bug (videos and sound play 2X fast and is sound is "crackly")? I think it's some sort of audio configuration problem, but I might be wrong. And lastly does anyone know if the camera problem is a lib problem or something with the kernel?
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
It's venturi because that's what was in the source. It had two definitions (venturi and smdk210) but for the 3.0 kernel for the nexus s, Google removed one of the smdk210 and left herring. I removed smdk210 which left me with venturi

As for the sound, it's an issue with how the sound driver is implemented and grabbed by the rest of the more important kernel source.

The camera I didn't even try to get working because I thought of it as a low-priority issue
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Camera is, and dont quote me, a lib issue. No one gas libs compatible with our cameras
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I know this but in which file it defines it? in mach-machine.c? Because I don't find it anywhere on the config.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Somewhere in mach-venturi.c defines the hardware name where the machine start code is
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
The interesting part is that when you did that it prevented the kernel from booting on my device - see my github for the commit that reverted it.

I've also made a bit of progress on audio in CM10, but mediaserver is still segfaulting.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Might be because I never updated my ramdisk file names on the github accordingly; so the init.smdk210.rc wasn't executed as init was looking for a file called init.venturi.rc but couldn't find it since I never renamed smdk210.rc to match the kernel

edit: so after looking at your github, you chose to revert the rename back to smdk110, which in effect did the same thing as renaming the init.smdk110 to init.venturi as it synced the device kernel name with the init script name.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Ok so I'll probably change everything to venturi then. Makes sense.
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
Another problem that needs to be fixed is the internal storage. It appears to be detected, but it just says the SD card is damaged. Any ideas?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
yes. If you look at the logcat (search for 'vold'), you'll see that it is trying to mount partition -1:-1 (which wraps arount to the numbers you see there), which does not exist. The prealpha has a similar problem, looking for partition 179:1. The correct one is 259:9. I have not figured out yet how to get it to choose the correct one, and until it does, it will fail the file system check (because it is not a FAT partition) and complain about being damaged.

@JackpotClavin: do you know why half of the partitions have a different major than the others? I think this is what's confusing it. There's a config var STORAGE_SHARES_DEVICE_MAJOR or spmething like that. In the pre-alpha, vold would never choose a major other than 179 - that of the device, like it was set. But the current build, with it set to false, it chooses -1 as the major.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Can I help in any way? I would love to run rom with project butter

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
Test out features and send them logs
[Samsung Galaxy Player 4.0, 5.0] KOala888:
but with development

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
read last few pages and go to his github and see if you can fix something..from what i read its name conflicts with kernel and rom source
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
I successfully decompiled the initramfs in the kernel and renamed "init.smdkc110.rc" to "init.venturi.rc" (as well as all the other init files with "smdkc110" in the name), but when I tried to re-compile the initramfs using a script, it said a certain compiler binary (gen_init_cpio) couldn't be found, even though I checked the script and it was indeed pointing to the directory that contained it. The zImage and initramfs decompiling/recompiling tools I used are listed below as a mediafire link, as well as a screen shot of the problem attached to this post. The kernel (zImage) is in the ZIP, as well as the decompiled initramfs from it, located in the output folder in the ZIP. (All files restored to original filenames.)

Kernel tools: http://www.mediafire.com/?dnphno7hqj86vv6
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Recommended way:

Download both kernel and initramfs from Github into side-by-side folders.

Modify what you want.

Export 'ARCH=arm' and set CROSS_COMPILE to your toolchain.

Then go to kernel directory and run 'sh build_yp_g70' or whatever the script is called. It will compile kernel and integrate ramdisk + modules.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
The biggest way anyone could possibly help right now is to examine logs, etc. and figure out what is causing problems with wi-fi and internal storage in the latest build i posted (Nov 10 I think). The other thing stumping me is why the kernel isn't getting flashed properly during rom installation.
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
Are you flashing in an ota package or with heimdall?

Sparx639