yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] tdm:
Yeah I tried the key code file. Not sure if it helped, didn't see any difference.

I tried setting PRODUCT_CHARACTERISTICS:=tablet but still getting the phone died error. Any hints? I'm assuming you don't have that problem.

The ramdisk is embedded in the kernel directly for these devices, it's not a separate structure like normal android devices. You need to recompile the kernel to change it.

Unless your kernel is from ambrice and has the modified init from teamhacksung, in which case I think it's separate. But I haven't looked at it yet and I don't know anything about it really.

I wrote a script to extract the ramdisk from a kernel binary, though, just in case you don't want to use Entropy512's for some reason.

I'm not on gtalk right now. I can hop on in a bit though.

---------- Post added at 01:40 PM ---------- Previous post was at 01:23 PM ----------

NM, I got it by removing ro.telephony.ril_class from my build.prop.
[Samsung Galaxy Player 4.0, 5.0] ambrice:
vold (which handles the sdcards) does not like the way the eMMC is partitioned on the 5.0. Out of the box, vold complains because partitions over p7 have a different major device number than the disk. Then if you get past that, vold does not like the fact that there is no p2 through p4 devices, it will wait forever for those before processing the disk.

To handle the first issue, I backported a kernel commit to allow for more than 8 partitions on an emmc device without changing major device numbers. For the second issue, I put in a hack in vold to declare the disk idle when the one partition you care about is there.

There's still some issue with the switchable mount points, it seems like vold is mounting both disks at /mnt/sdcard now for some reason..
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
stock vold do anything?
[Samsung Galaxy Player 4.0, 5.0] ambrice:
Stock vold handles it, Samsung has some patched version of vold which we don't have access to. The stock vold has a lot of log messages that aren't in the AOSP source.
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
You guys are too great! I just used up my 8 thanks limit, will get back to it tomorrow! I can't believe we will actually be getting ICS! I wish I knew a little about programing to help you! Keep up the great work!
[Samsung Galaxy Player 4.0, 5.0] tdm:
How did you get sound working?

And I'm still not able to get the stupid home button working. EventHub registers code 102 and I've got but nothing happens on the screen. :/
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
you pushed both .kl files from my device setup? and i just pushed sound

edit: stock vold got my the internal storage to mount at /mnt/emmc and the external /mnt/sdcard to mount at /sdcard which is exactly what we need... except for the fact that for some reason, /mnt/sdcard is not properly symlinking to /sdcard so if i try to open /sdcard in root explorer it won't let me saying the sdcard isn't mounted, but it will allow me to browse the sdcard contents when i click /mnt/sdcard... it's a problem with init.rc and i'll look into it a little later.. i gotta experiment with this new ramdisk on samsung devices that i've never used before
[Samsung Galaxy Player 4.0, 5.0] tdm:
Thanks for audio, I'll take a look.

Yeah I pushed the .kl files. HOME still doesn't work, but MENU and BACK do.

Here's the setup on the ypg1:

/dev/input/event7 => softkeys/touchscreen, driver qt602240. EventHub output:

path='/dev/input/event7'

name='qt602240_ts_input'

classes=0x15

configuration='/system/usr/idc/qt602240_ts_input.idc'

keyLayout='/system/usr/keylayout/qt602240_ts_input.kl'

keyCharacterMap='/system/usr/keychars/Generic.kcm'

builtinKeyboard=false

qt602240_ts_input.idc is your cytma340_input.idc unmodified.

qt602240_ts_input.kl is your cytma340_input.kl unmodified.

I cranked up logging on EventHub. When I press HOME, I get this:

I/EventHub( 139): /dev/input/event7 got: t0=62, t1=164671, type=1, code=102, value=1

I/EventHub( 139): event time 62164671000, now 62165015879

I/EventHub( 139): iev.code=102 keyCode=3 flags=0x00000002 err=0

I/EventHub( 139): /dev/input/event7 got: t0=62, t1=164743, type=0, code=0, value=0

I/EventHub( 139): event time 62164743000, now 62165015879

I/EventHub( 139): /dev/input/event7 got: t0=62, t1=242990, type=1, code=102, value=0

I/EventHub( 139): event time 62242990000, now 62243294002

I/EventHub( 139): iev.code=102 keyCode=3 flags=0x00000002 err=0

I/EventHub( 139): /dev/input/event7 got: t0=62, t1=243047, type=0, code=0, value=0

I/EventHub( 139): event time 62243047000, now 62243294002

When I press BACK, I get this:

I/EventHub( 139): /dev/input/event7 got: t0=86, t1=773022, type=1, code=158, value=1

I/EventHub( 139): event time 86773022000, now 86773374502

I/EventHub( 139): iev.code=158 keyCode=4 flags=0x00000002 err=0

I/EventHub( 139): /dev/input/event7 got: t0=86, t1=773092, type=0, code=0, value=0

I/EventHub( 139): event time 86773092000, now 86773374502

I/EventHub( 139): /dev/input/event7 got: t0=86, t1=877055, type=1, code=158, value=0

I/EventHub( 139): event time 86877055000, now 86877124629

I/EventHub( 139): iev.code=158 keyCode=4 flags=0x00000002 err=0

I/EventHub( 139): /dev/input/event7 got: t0=86, t1=877066, type=0, code=0, value=0

I/EventHub( 139): event time 86877066000, now 86877124629
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
could it be that you're using a international kernel?

the boot.img from ambrose that i'm using is in the zipstuff folder of my device folder

edit: holy **** this thing has pretty good sound
[Samsung Galaxy Player 4.0, 5.0] tdm:
Nope definitely not an intl kernel. Same kernel works great with CM7.

---------- Post added at 03:56 PM ---------- Previous post was at 03:13 PM ----------

Tried your audio files. Built fine but I'm gonna need to dig to find out what's wrong:

W/AudioPolicyManagerBase( 80): getOutput() could not find output for stream 1, samplingRate 0, format 0, channels 3, flags 0
W/AudioPolicyManagerBase( 80): getOutput() could not find output for stream 1, samplingRate 0, format 0, channels 3, flags 0
W/AudioPolicyManagerBase( 80): getOutput() could not find output for stream 1, samplingRate 0, format 0, channels 3, flags 0
E/SoundPool( 137): Error creating AudioTrack
I/AudioService( 137): AudioFocus requestAudioFocus() from android.media.AudioManager@4130f210com.android.music.MediaPlaybackService$3@412f0d38
I/AudioService( 137): Remote Control registerMediaButtonIntent() for PendingIntent{41508448: PendingIntentRecord{415082c8 com.android.music broadcastIntent}}
E/MediaPlayer( 679): Attempt to call getDuration without a valid mediaplayer
E/MediaPlayer( 679): error (-38, 0)
E/MediaPlayer( 679): start called in state 0
E/MediaPlayer( 679): error (-38, 0)

---------- Post added at 04:30 PM ---------- Previous post was at 03:56 PM ----------

Hmm, interesting that you're using all those alsa config files. I don't have alsa on my ics rom for my phone.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
ahh **** i forgot to throw those in the build. i'll put them in the vendor folder later
[Samsung Galaxy Player 4.0, 5.0] Wheatly:
Sorry if I'm not contributing, but is it possible to make the camera to record HD and have better focus?
[Samsung Galaxy Player 4.0, 5.0] tdm:
The project I created is named davignola (github.com/davignola). Vignola was a famous Italian architect from the 1500's, and a contemporary of Palladio.

I'll start loading up the github with files soon. My plan is to have the following repos:

android_device_samsung_venturi

android_vendor_samsung_venturi

android_device_samsung_palladio

android_vendor_samsung_palladio

android_kernel_samsung

The first four will have gingerbread and ics branches. The kernel may or may not have different branches for venturi and palladio, depending on how different the code is between them.

I've also been thinking quite a bit about unifying the ROMs. As far as I can tell, the major (only?) difference between the 4.0 and 5.0 is the block devices. My understanding is that the 4.0 has both an MTD and an MMC, while the 5.0 only has an MMC. The "kernel" is actually a kernel+initramfs which contains the rc-files and such which are responsible for block device mounting. So I think the only things we'd need to take care of outside the kernel are vold.fstab and the installer edify script. Does that sound accurate? Did I miss anything?
[Samsung Galaxy Player 4.0, 5.0] Tecardo:
Should we make a test build of your cm7 for 4 and 5 and look where the difference is? As I know the 5 and 4 have other screen orientations.

And the things you noted above. For the eu rom , we only need another kernel?

Gesendet von meinem YP-G1 mit Tapatalk
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Sounds good. Do you have wifi working on your builds? Mine can see my networks but cannot connect for some reason
[Samsung Galaxy Player 4.0, 5.0] ambrice:
I have wifi sort of working, but it's flakey.. Sometimes it would fail to connect, but then if I rebooted the player with it "remembering" that network it would connect on startup.
[Samsung Galaxy Player 4.0, 5.0] tdm:
That's a good idea, I can try to make a dual 4/5 CM7 ROM in a few days. But there's lots of things to fix first.

In addition to the kernel and block devices, they also have different touch screen hardware. But the config files for touch screen are very small so we can include both easily without bloating the ROM.
[Samsung Galaxy Player 4.0, 5.0] noisyfox:
Have you edited the keylayout files in /system/usr?

I have the same problem when I was testing CM7. Then I edit the s3c-keypad.kl and add

key 102 HOME WAKE_DROPPED

then it works.
[Samsung Galaxy Player 4.0, 5.0] tdm:
No, wifi wasn't working for me. It found the AP and then wpa_supplicant kept failing to auth.
[Samsung Galaxy Player 4.0, 5.0] ambrice:
Sounds good. Is davignola set up as an organization? It seems to be a regular member account.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Yeah it's currently a regular member account, I just reserved it for now. But there's an option to convert it into an organization account. I've never used an organization account, can you briefly explain what it is and why it would be helpful?
[Samsung Galaxy Player 4.0, 5.0] ambrice:
Maybe I'm making assumptions about the plan, but I was assuming you were setting up a central account that we could all push changes to? How will the davignola repositories work?

I've never used one either, but if it's an organization you could add our individual accounts as members with access to push to the repositories.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Yeah I definitely want a central account that we can all push to. But like I said, I never setup an organization account on github before. I'll need to do some reading to figure out how it works.
[Samsung Galaxy Player 4.0, 5.0] Tecardo:
Looking after it :) When your ROM is ready i want to port it to the eu version.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
So is this wifi issue kernel related or /system related? I can't build kernels for some reason as wifi never works and it won't even let me turn it on.. that's how borked it is
[Samsung Galaxy Player 4.0, 5.0] tdm:
Not sure. Maybe it's a mismatch between kernel and system.

CM7 is happy with wifi on this same kernel.

CM9 on my VM670 is happy with wifi on this same build tree.

---------- Post added at 02:53 PM ---------- Previous post was at 02:12 PM ----------

ok it's an organization now.

---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------

Also, as for the kernel and initramfs thing....

ambrice switched to a different initramfs setup from teamhacksung. I haven't looked at it yet but I think it's a two-stage thing where the builtin initramfs is a stub that loads the second stage initramfs from somewhere else (maybe /system?) The motivator for this was so that the init files under the device tree would actually be used and reflect what's running on the device. ambrice, does that sound correct?

I need to investigate this further. But another option is to put the kernel sources in the repo manifest and the initramfs files in, say, the device tree, and reference the device tree in the kernel build.

Thoughts?

---------- Post added at 03:31 PM ---------- Previous post was at 02:58 PM ----------

Just looked at his commit. It uses mmcblk0p11 for the second stage. What does that normally hold on a 5.0 device?

---------- Post added at 03:41 PM ---------- Previous post was at 03:31 PM ----------

Ok so venturi_usa_ota_from_target_files writes into the edify script to flash boot.img on both mmcblk0p11 and mmcblk0p12. So that's the kernel boot.img.

Still digging. An explanation of how this fits together would be nice... :)
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
i'll patch the python scripts to make it so we don't have to add files afterwards
[Samsung Galaxy Player 4.0, 5.0] tdm:
Actually, after looking at that 2-stage boot script, I'm thinking it's kinda... well, hacky. Clever but hacky.

I just thought of something that is more in line with normal devices. Say we build the kernel with a big, empty placeholder file for the initramfs. Then we fill that in with the boot and recovery ramdisks in the main build. It would be kinda like creating boot.img. The only differences really, would be that (1) the boot ramdisk goes into the kernel instead of building a boot image -- same concept, really, just a slightly different implementation, and (2) the recovery gets put in there also instead of building a separate image.

Sounds like a clean and elegant solution to me.... someone tell me what I missed or why it won't work. ;)
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
sounds like you got it. the stock samsung ramdisk is actually IN the kernel. what the teamhacksung team did was replace the init binary that usually goes in the kernel with a script called init that the kernel calls that basically says "act like a normal kernel/ramdisk combo" which basically extracts the ramdisk that gets added on when we build the boot.img from the way normal boot.imgs are made. so that init script that has replaced the init binary extracts the "new" ramdisk that's made in the cm boot.img process and that replaces the init script with the actual init binary and the rest of the *.rc scripts that gets built from source, then it executes the init binary that cm made

this wifi is turning out to be a real PITA. gonna skip it for now. which other bugs do we have? and can somebody send me their .zip that has wifi that at least connects at times? so far with my builds, i've had absolutely 0 connections with my wifi and i've been told that some of you guys at least have some which is better than nothing. which other bugs do we have that can be tested and fixed without wifi?
[Samsung Galaxy Player 4.0, 5.0] tdm:
Okay so my plan sounds solid? I'll start implementing that in the morning.

I'll try to get my cm9 files on github later tonight but no promises. Tomorrow AM at the latest. My wife and infant are really sick with the flu so my hands are full for the evening... :/
[Samsung Galaxy Player 4.0, 5.0] tdm:
My github device and vendor trees are updated on both gb and ics branches. Still working on the kernel import.

github.com/tdm
[Samsung Galaxy Player 4.0, 5.0] Tecardo:
Look at /data/misc/wifi and then the wpa_suplicant.conf

It could be, that it don't saves the values

Can you give me your ROM? Or do you have both in git?

Gesendet von meinem YP-G1 mit Tapatalk
[Samsung Galaxy Player 4.0, 5.0] Jayydude_SGP:
When the US 5.0 ROM is ready I'd be happy to test :)

Sent from my Galaxy Far Far Away Player 5.0
[Samsung Galaxy Player 4.0, 5.0] ambrice:
I don't see any advantages to this approach. As for (1), why do we care if the ramdisk is contained within the kernel? It isn't for all other android devices.

As for (2), the teamhacksung approach does include the regular boot ramdisk and the recovery ramdisk in the same image. This is the script that creates the boot.img:

https://github.com/ambrice/android_device_samsung_venturi_usa/blob/master/mkshbootimg.py

It basically concatenates the kernel, the regular boot ramdisk (gzipped cpio archive) and the recovery ramdisk. Then it adds lines in the boot.img binary like:

BOOT_IMAGE_OFFSETS

boot_offset=7336;boot_len=1093;recovery_offset=8429;recovery_len=3493;

The very small initramfs init script does the grep for those lines, and uses those values to pull either the boot ramdisk or the recovery ramdisk out of the boot.img, and decompresses it as the root filesystem and runs its init.

The init script is here:

https://github.com/ambrice/linux_kernel_galaxyplayer/blob/master/usr/venturi_initramfs_files/init

I think it would be much easier to use this approach with your kernel instead of inventing a third approach.
[Samsung Galaxy Player 4.0, 5.0] ambrice:
tdmcode, I've pushed a commit to my fork of Entropy512's kernel at https://github.com/ambrice/linux_kernel_galaxyplayer

I added a yp_g1_usa_defconfig by applying the differences between palladio_usa_defconfig and venturi_usa_defconfig to Entropy512's yp_g70_usa_defconfig.

In addition, I added the start of a palladio initramfs under usr/. But the block devices there need to change (I'm not sure what they are), and then you would need to copy some things out of your old initramfs into your device tree..

As a first step, it would be interesting to clone the kernel, override the initramfs with your current initramfs, and see if the resulting kernel runs on your CM7. If that works, then we could at least be using the same kernel tree.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
this wifi is such a PITA
[Samsung Galaxy Player 4.0, 5.0] turbanator:
Reading as you guys build this is both fascinating and entertaining. Sounds like excellent work so far, I hope tdm's wife and child get well soon!

I'm really looking forward to seeing the results, though I'm not experienced at all to provide help building this, I'll do my best at thoroughly testing it!
[Samsung Galaxy Player 4.0, 5.0] Tecardo:
JackpotCalvin, Do you think it could be the bug I mentioned?

@zac: I have found a reference to holo in miui. Changed it. I will sent it to you later.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Ok thanks!
[Samsung Galaxy Player 4.0, 5.0] tdm:
One reason is that by putting the ramdisk into the kernel instead of using a two stage process, you don't need to grep a binary partition (dangerous!) Another is that you don't need to copy the data twice.

Quite honestly if I was really inclined to do the initramfs with teamhacksung's mkshbootimg.py, I'd rewrite the kernel early init stuff to grab it directly. But it's easier to just reserve space and fill the space in.

Really the practical difference here is whether the initramfs is embedded in the kernel binary or tacked onto the end.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
okay awesome, got wifi working :-)

edit: one weird thing is that the signal bars don't show up next to the battery. if i open the wifi menu, the list of networks have the signal strength in bars, but when it's connected, on the top by the battery level meter shows no bars
[Samsung Galaxy Player 4.0, 5.0] ambrice:
Why is grepping a binary dangerous? You're right that the teamhacksung approach has an extra copy, but in the normal case the ramdisk it uses is much smaller than yours will be (538K) because you'll have to put the recovery binaries into the same ramdisk. Not only that, but you'll have to allocate more space than you need because you won't know at kernel compilation time how big your ramdisk will be.

I would like for us to use the same kernel tree if possible for the 4.0 and 5.0, but I don't see any advantage in switching the system I have that's working (and is the standard for samsung devices) to this new approach.

---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------

What was the fix?
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
custom dhcpcd and init.local.rc that has a few things added to it
[Samsung Galaxy Player 4.0, 5.0] tdm:
Because you are never 100% guaranteed that it won't give false positives or false negatives. It's a tool for text, not binaries.

All true. Neither solution is perfect, they both have flaws.

What I'm probably going to end up doing first is creating a small statically linked executable to use for /init that does the job of that script+busybox. That's pretty easy and should serve as a nice middle ground between our two approaches.

Then later I'll look into modifying the kernel initramfs loader to grab the final initramfs directly instead of using a two stage setup. This will surely take more time to implement so I doubt it will be done for a few weeks.

Does that work for you?

Certainly using the same kernel tree would be nice. I haven't diffed the two trees yet, have you?
[Samsung Galaxy Player 4.0, 5.0] noobnl:
Since the galaxy player uses BML layout, you will have problem in the future if you don't use 2 stage initramfs and switch to MTD.

You need to bypass BML bootloader configuration file which is stored in BML6 which has a mount point of /mnt/.lfs/.

We have no access to that partition in MTD because it uses a special FS called j4fs.

j4fs kernel module is linked to the bml kernel module.

Another issue is the configuration has it own editor that clear the function and set the bootmode for the next boot and boot from that mode. that is called param kernel module. it is linked to bml and j4fs

We had to get rid of those thing because we wanted a tainted free kernel.

it will stay in one mode and stay like that till we switched to bml kernel so it would clear the mode.

I have the epic so if the trigger to boot into bml8 or bootloader see a request to boot into a mode in param.lfs which is in mtd kernel and if i don't clear that mode it will stay in recovery kernel which is in bml8 and boot kernel is in bml7.
[Kindle Fire General] itsDefying:
Yeah, so I accidentally reset my kindle, and then it rebooted into TWRP then wiped the files, and now it keeps booting into TWRP. I tried installing the 6.2.1 update and CM7 and neither work. Please help? :(
[Kindle Fire General] Groovehog:
You need to change the bootmode. If ADB is working just type:

adb shell

idme bootmode 4000

reboot

Should boot normally after that. Cheers.
[Kindle Fire General] Kekule:
I had soemthing similar happen and I had to reinstall the usb driver to get it recognizing the kindle again
[Samsung Galaxy Nexus] dricacho:
Hello everyone,

My current phone is the 1st gen of the Galaxy S - Fascinate running on MIUI 1.12.16 with Glitch v13. I've had a blast tinkering with this phone, flashing different cool ROMS and tweaks in it. But after a year, I think it might be time to get into something new and more exciting. Since I've heard of the upcoming G-Nex, I was waiting for it in anticipation. They were really hyping up the ICS, I think it was cool especially the face unlock & touch to beam. I went to a Verizon store the day it came out and played with the phone. But didn't get to spend much time on it since there's a line for it and a Verizon sales person that's standing there making sure I don't take too long on it. I walked out of the store unexcited about it. I can't exactly pin-point the reason why. The ICS GUI looks nice the screen appears nice and all, the response seems ok, just nothing that blew me away. I can tell the floor model was dropped because the back cover is not sitting flush anymore no matter how much I tried to push it in, maybe some retainer clip broke inside. I am still thinking about visiting again to take a look. However, I'd like to know from you guys, who've been playing with this phone, what you think about this phone. What do you like most and what did you like the least? I'm more concerned about the hardware aspect of the phone because we all know that software can always be altered, updated, or changed. Would you recommend this phone??

Any input would be greatly appreciated.
[Samsung Galaxy Nexus] dario3040:
Hardware is the least thing you should worry about.

This phone pretty much has it all.

Closest thing in hardware has to be the iPhone 4S, followed by the Galaxy S II.