DELETED

Search This thread
By:
Advanced…
M

Meticulus

Guest
Installation Instructions

Comming from a Pre "Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839" ROM
  1. Do a back up!
  2. Do factory reset/ wipe (incl. /system)
  3. In recovery: flash ROM zip file. (You WILL get an assert error!)
  4. Read the warning on the screen.
  5. Flash the ROM again!
  6. If you have and international device flash the INT Kernel from the OP.
  7. Flash Gapps
  8. Reboot.

Comming from "Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839" ROM or later

  1. Do a back up!
  2. Do factory reset/ wipe (incl. /system)
  3. In recovery: flash ROM zip file.
  4. Ignore the warning on the screen.
  5. If you have and international device flash the INT Kernel from the OP.
  6. Flash Gapps
  7. Reboot.
 
Last edited:
M

Meticulus

Guest
Change Log:


NOTE: All future changelogs will be attached below!

Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839 --> Slim-venturi-4.4.2.beta.1.9-UNOFFICIAL-20131223-1727 changes:

SlimRoms/frameworks_base:
  • 2013-12-22: systemUI: fix notification dissapearing during recreation and possible <@Lars Greiss>
    Code: 
    app crashes due that binded notifications are not there anymore

as well small cleanup

Change-Id: Ieed143088a55693fc56e6526e6b349d72b7b25cc
  • 2013-12-22: Merge "fb: use SlimActions for torch tile and send as qualified user" into kk4.4 <@Gerrit Code Review>
  • 2013-12-22: Merge "fb: lock statusbar recreation and release after ticker is done" into kk4.4 <@Gerrit Code Review>
  • 2013-12-22: fb: use SlimActions for torch tile and send as qualified user <@Lars Greiss>
    Code: 
    the broadcast and do not collape the panel bar

as well send with qualified user the IME switcher broadcast.

Change-Id: Ibad8b4f908e6d701999712f58b9996cd7a805fc4
  • 2013-12-21: fb: lock statusbar recreation and release after ticker is done <@Lars Greiss>
    Code: 
    In rare cases it happens that the ticker call just happened and a recreation
was called which results in a crah due of the missing binder.
To avoid it lock the recreation when a ticker call is in progress
and release it after it is done and notify the recreation to go ahead

Change-Id: Iedbf858bdb2ac2ad97563e344a571b384e17cfc7
  • 2013-12-21: trds:[framework] dark images adjustments <@kroz>
    Code: 
    Change-Id: Ie038c4a1aa535708c23f099fb5e836407e3d1603
SlimRoms/packages_apps_Camera2:
  • 2013-12-22: TrueView Returns! <@Gerrit Code Review>
    Code: 
    This adds the ability to view the complete sensor frame image
rather than the cropped preview used by AOSP to fill the entire
surface.

Change-Id: I79b14a165c66fa4f8b8e43598bd6a80e4de1c08b
  • 2013-12-22: Fix Smart Capture label display <@Lars Greiss>
    Code: 
    Change-Id: Ia3cceda0bf7fec21f2d019f07d416bfe8ebf211d
  • 2013-12-22: Fixes Mako continues focus problem <@Lars Greiss>
    Code: 
    rebase

Change-Id: I25187998003d357ec5ed3b10329fb39941f47bea
Signed-off-by: Josue Rivera <prbassplayer@gmail.com>
  • 2013-12-22: camera: Add ZSL support for Samsung/Qualcomm cameras <@Lars Greiss>
    Code: 
     * Preview management for Samsung/Qualcomm cameras

Patchset 3: merge conflicts fixed
            build errors fixed

PatchSet 4: codestyle corrections

Change-Id: Ib36bd21c9a76b45bced3eee2f25acc35b5d82b30
SlimRoms/packages_apps_InCallUI:
  • 2013-12-21: Merge "TRDS: Dark InCallUI" into kk4.4 <@Gerrit Code Review>
  • 2013-12-19: TRDS: Dark InCallUI <@kroz>
    Code: 
    PS2:
- moved into right folder

PS3:
- redirect colors of original layout xml

Change-Id: I5bcfeb692bc4653e240df7c47216826452ee7d47
SlimRoms/packages_apps_Settings:
  • 2013-12-22: Merge "First translation of Settings for KitKat" into kk4.4 <@Gerrit Code Review>
  • 2013-12-18: First translation of Settings for KitKat <@gwindlord>
    Code: 
    "Go To Sleep" paraphrased

Removed whitespace

Change-Id: I666cb60da3a0751ba1d4f351c2a46b1b159d9dd3
SlimRoms/packages_apps_Torch:
  • 2013-12-22: Torch: add better error handling and added fallback mechanism <@Lars Greiss>
    Code: 
    The handling of the Torch if an exception occured was very bad and
it was easy to break:

- notify the user with toast if the camera interface is not pressent
- catch the case that sys led controlled devices have wrong permissions
  (eg third party kernel) and torch will completly crash.
  Checking now if sys init is present.......if not successful
  try to switch back to the camera interface.
- send broadcast change only if the state really switched
- when error occured turn off the service and the notification
- cleanup
- send broadcast with qualified users

Change-Id: Iabeb3b5f1c17d784a06c154f9a33e8d3d5214b7d
  • 2013-12-21: make torch to a real system app <@Lars Greiss>
    Code: 
    give it the correct permissions to allow to write
to sys interface with less permissions needed to
keep security alive

Thanks Alex for the hint to the hidden API

and gmillz for the idea

Change-Id: I44f70bdf3ecfb57ccac85eebe61e57a163bdf501
SlimRoms/vendor_slim:
  • 2013-12-22: push to 1.9 <@Lars Greiss>
    Code: 
    Change-Id: I4c4aab6fbd8440cda3649b1d77351aa0563dd15c
  • 2013-12-22: push to 1.8 for weekly <@Lars Greiss>
    Code: 
    waiting for feedback on last patches then we start jenkins

Change-Id: I1b8f5dcb6f8620506dfc4399b75c56802a3bd8e1


Older logs:

  • 2013-12-22: clean up: movefiles.sh is no longer needed... <@Meticulus>
  • 2013-12-22: overlay: SlimCenter overlay for ota. <@Meticulus>
    Code: 
    -I've found that with just a few small adjustments you can redirect
SlimCenter to another url to check for updates.
  • 2013-12-22: overlay: BOARD_USE_LEGACY_TOUCHSCREEN device tree flag. <@Meticulus>
    Code: 
    -Everytime I repo sync my framework base commit to fix the touch screen
gets wiped out. In order to preserve it, I'm putting it in the overlay.
  • 2013-12-20: ota: testing <@Meticulus>
  • 2013-12-20: LVMv2: phase out the use of mmcblk0p14 as extra space. <@Meticulus>
    Code: 
    -With the implementation of LVMv2, we don't need to use mmcblk0p14
(/vendor, /system/vendor) as extra space.
-mmcblk0p14 is now in the logical volume group "lvpool" along with
mmcblk0p13 and mmcblk0p16.
  • 2013-12-20: ota: change device name from venturi to YP-G70 <@Meticulus>
  • 2013-12-20: ota: removed beginning and ending spaces.. <@Meticulus>
  • 2013-12-20: ota: ota update manifest. <@Meticulus>
    Code: 
    -Initial commit of the ota manifest.
  • 2013-12-19: slim.mk: build type switch. <@Meticulus>
    Code: 
    -Switch from common full tablet to common full hybrid...
  • 2013-12-19: init.venturi.rc: fix a small typo.. <@Meticulus>
  • 2013-12-19: LVMv2: add lvm services to init.venturi.rc. <@Meticulus>
    Code: 
    -This was left out of my initial commit here:
https://github.com/Meticulus/slim_device_samsung_venturi/commit/7ccd47c874f9a00c0397c8e8f17f3faaf72e256b

-This is absolutly neccessary for LVM...
  • 2013-12-19: twrp: Correct screen resolution. <@Meticulus>
  • 2013-12-18: LVMv2: initial implementation system(600M) <@Meticulus>
    Code: 
    -Logical Volume Management

-The YP-G70 only has a 290m /system partition and this is not enough
to accomodate KitKat + full gapps. So, I'm implementing LVM so that
we can get dynamic volume resizing without having to change the under-
lying partitions.

-Partitions in Logical Group (Aprox 2.1G)
-- /dev/block/mmcblk0p13 (normally /system)
-- /dev/block/mmcblk0p16 (normally /data

-Logical volumes
-- /dev/lvpool/system (600M)
-- /dev/lvpool/data (100% remaining, aprox 1.5G)

-Installation Notes
--On the first flash, if the system logical volume is not present or
is less than 600M there is an assert error. This is so that if anyone
needs to backup information contained in /data, they can. In order to
proceed with the installation, the zip must be flashed a 2nd time.
--During the 2nd flash partitions in the logical group are wiped and
the logical volumes are created and formated then the /etc/fstab and
/etc/recovery.fstab are switched so that, when we hand everything off
to the normal rom installer, the new logical volumes are mounted.

-Reverting to a PRE-LVM ROM
--In the YP-G70 the "recovery", be it CWM or TWRP and in the kernel's
recovery-ramdisk. So in order to get a different recovery you just
flash a different kernel. So to get back to a PRE-LVM ROM, you just:
1. Reboot to recovery like normal.
2. Flash your PRE-LVM ROM like normal.
-- Note: All we really care about at this point is that the kernel
(boot.img) gets flashed. Ignore any other errors!
3. After the flash, Power off.
4. Hold volume up and power on, till you get to recovery.
5. Full wipe, including /system
6. Flash ROM + Gapps like normal

-Future Considerations
--LVMv2 allows us to quickly change the size of the system partition
as Android grows in size without having to manually repartition.
Manually repartitioning might cause unforseen problems with legacy
software.

-Meticulus
  • 2013-12-17: recovery init: adb without /system <@Meticulus>
    Code: 
    This allows "adb shell" to function when /system partition is not mounted
or for any reason /system/bin/sh is unavailable.
When /system IS mounted then adb uses mksh is used via /system/bin/sh
When /system IS NOT mounted then adb uses busybox via /sbin/sh
  • 2013-12-14: Removed torch from build. <@Meticulus>
    Code: 
    Torch isn't working at the moment anyways. May readd later!
  • 2013-12-14: twrp: defined custom power key and fixed screen timeout problem. <@Meticulus>
  • 2013-12-14: Initial commit <@Meticulus>
 

Attachments

  • Slim-venturi-4.4.2.beta.1.9-UNOFFICIAL-20131223-1727-change.log.txt
    4.7 KB · Views: 77
  • Slim-venturi-4.4.2.beta.2-UNOFFICIAL-20131231-1223-change.log.txt
    108.2 KB · Views: 19
  • Slim-venturi-4.4.2.beta.2.1-UNOFFICIAL-20140105-0839-change.log.txt
    25.9 KB · Views: 44
  • Slim-venturi-4.4.2.beta.2.3-UNOFFICIAL-20140114-0943-change.log.txt
    55.3 KB · Views: 17
  • Slim-venturi-4.4.2.beta.2.4-UNOFFICIAL-20140121-0903-change.log.txt
    31 KB · Views: 25
  • Slim-venturi-4.4.2.build.2.5.RC1-UNOFFICIAL-20140129-1514-change.log.txt
    36.1 KB · Views: 103
Last edited:
Lorddemonrage

Lorddemonrage

Senior Member
Aug 19, 2013
63
18
BAH!! y u release while i'm at work....

Gonna test when i get home....

Flashy flashy, its like Christmas but better! no wrapping paper to clean up or relatives to dispose of.
 
64kb

64kb

Senior Member
Aug 19, 2012
64
19
Hamilton
Somehow I knew I would come on today to find KitKat available. Trying it now, will update later.

EDIT: No options for hardware buttons?
 
Last edited:
M

Meticulus

Guest
iurnait said:
Very nice. How did u solve the dalvik cache issue?

Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse

I didn't really solve it, per say. I put in a cheap hack to change the permission of the directory: in the init.venturi.rc. I'll got some clean up to do, but I'll be pushing my device tree tomorrow and submitting some changes to yours so we can get CM11.;)
 
M

mr_ggcstop

Member
Mar 11, 2012
32
14
Odessa
Hello! Thanks for your work! I tested this rom, it's pretty nice. The only bug (except known) is that TWRP is not working on INTL kernel.
 
Lorddemonrage

Lorddemonrage

Senior Member
Aug 19, 2013
63
18
had sometime to mess with it. my sd card is not showing up, lost super user access. other than that almost everything works fine.

elaborating, i can see sd card in file manager, but connecting to windows does not show sd card accessible, just the galaxy players internal memory
 
Last edited:
M

Meticulus

Guest
mr_ggcstop said:
Hello! Thanks for your work! I tested this rom, it's pretty nice. The only bug (except known) is that TWRP is not working on INTL kernel.
Click to expand...
Click to collapse

TWRP is a "known issue", if you read the OP.:eek: (workin' on it)

Lorddemonrage said:
had sometime to mess with it. my sd card is not showing up, lost super user access. other than that almost everything works fine.

elaborating, i can see sd card in file manager, but connecting to windows does not show sd card accessible, just the galaxy players internal memory
Click to expand...
Click to collapse

I am aware of the "2 cards in mass storage issue", but for the su problem, haven't had any issues .... developer-options-> root (or something like that):confused:

joemhewitt said:
Does it need a wipe if coming from 4.3

Sent from my zx spectrum
Click to expand...
Click to collapse

yes including system:good:
 
bassbrick15

bassbrick15

Senior Member
Jul 8, 2013
84
33
When will the TWRP fix be released? My US player now, after the flash using Clockworkmod, will not be recognized in odin when in download mode. I love kitkat but i want to go back to my cm10.2 build. And the only way to do that as i know is to go to gingerbread and upgrade from there. but because of this issue i am stuck with TWRP and no os on my USA galaxy player 5.0. Please advise!!!!
 
M

Meticulus

Guest
bassbrick15 said:
When will the TWRP fix be released? My US player now, after the flash using Clockworkmod, will not be recognized in odin when in download mode. I love kitkat but i want to go back to my cm10.2 build. And the only way to do that as i know is to go to gingerbread and upgrade from there. but because of this issue i am stuck with TWRP and no os on my USA galaxy player 5.0. Please advise!!!!
Click to expand...
Click to collapse

  1. Do not ask for ETA's!
  2. READ THE OP BEFORE FLASHING!!! THE OP CLEARLY STATES NOT TO FLASH UNLESS YOU KNOW WHAT YOU ARE DOING BECAUSE TWRP IS NOT WORKING!
 
FweaKiid305

FweaKiid305

Senior Member
Apr 1, 2012
100
10
Miami
Been Waiting For This For Awhile Noe. Thanks Guys, I Guess With Patience Good Things Come. Hopefully The Same Can Be Said About The Rear Camera.

Sent from my YP-G70 using xda app-developers app
 
coffee-turtle

coffee-turtle

Senior Member
Jun 23, 2011
358
126
Meticulus said:
  1. Do not ask for ETA's!
  2. READ THE OP BEFORE FLASHING!!! THE OP CLEARLY STATES NOT TO FLASH UNLESS YOU KNOW WHAT YOU ARE DOING BECAUSE TWRP IS NOT WORKING!
Click to expand...
Click to collapse

Hi Meticulus!

First, let me thank you for all your time and energy spent in making this mod for an old device! I love my Player 5, but it is show it's age. I'm hoping your SlimKat 4.4.1 will breathe new life into it. (A shame Samsung stopped developing this line).

I have a Galaxy Player 5 running a rootedGingerbread 2.3.5 with CWM v5.0.2.7 (no TWRP)

Do you recommend any special preparation before applying SlimKat 4.4.1?
Since I'm using CWM, will I be able to restore back to Gingerbread using a current backup (just in case)?

As you might have guessed, I am not a frequent "mod"-er so I've fallen behind a bit.

Thank you for taking your time to help me and so many others!
 
You must log in or register to reply here.

Similar threads

DoeBoi
[Q] Rooting Samsung Galaxy Player YP-G70 (5.0 wifi)
Replies
497
Views
263K
zaclimon
zaclimon
eng_matt
[ROM] Eryigit-GB-2.3.6 G70ZCKPA Galaxy Player 5.0 For USA and INT (Rls:3.5) {UPDATED}
Replies
381
Views
197K
kings121
kings121
JackpotClavin
[ROM] CM9 (ICS) for the Galaxy Player 5.0 USA
Replies
445
Views
138K
H
hanjosep
R
[KERNEL][CWM][OC&UV] rj's custom kernel for Galaxy Player 5.0 INTL (YP-G70) r14
Replies
232
Views
152K
necktru
necktru
A
[Q] Galaxy Player 4.2 (YP-GI1) - Rooting and ROMs
Replies
750
Views
187K
warwound
warwound

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    K
    KOala888
    Wow, I hadn't realise that we have a new delevoper here and working kitkat :eek:
    Amazing job guys, I am proud that I could be a part of our community :)
    Keep it up!


    And I am sorry that I sort of vanished, but I had my player stolen, so unfortunatelly I can't event taste 4.4.
    I tried to compile some stuff, but my laptop with windows 8 and new tricky boootloader doesn't work well with ubuntu on ush HDD.
    Now when I study IT I finally understand the kernel code :D

    GOOD LUCK with development!
    View
    4
    M
    Mevordel
    Meticulus said:
    I'm still seeing how much I can get out of the rear cam paradigm shift. Sunday, there should be a version number change in slim ( needed for ota ) and if I have enough time, I'll release a build then. Source ( and release if not Sunday) will come Monday . I got to commit my changes then, prepare pull requests for CM.

    Let me just say that from a technical point of view, I didn't really "fix" the camera. What I did was, chip away at the camera HAL until the rear cam functioned the same as the front cam. I even got so far as to have the jpeg encoder size the images up to a 3mp resolution ( or what ever you have selected) but you can tell the images are not 3mp because of the file size. It's a compromise but it does allow the rear cam to work from a practical standpoint.:D

    BTW, Hows the kernel going?:highfive:

    P.S. Torch working now too!:good:
    Click to expand...
    Click to collapse

    I figured out the reason the kernel only saw 12 partitions was because somehow my device only had 12 partitions :facepalm: So all that's left now before I try booting Android is to get the regulators working. I'm going to see if I can copy Aries on that one. I pretty much had to rewrite the framebuffer driver, but video does work now.
    View
    2
    I
    iurnait
    annoyingduck said:
    What app are you using to get each build entry separately listed like that? It looks like root Explorer on the bottom, but not the rest...
    Click to expand...
    Click to collapse

    Its ROM toolbox

    Sent from my Nexus 7 using Tapatalk
    View
    2
    M
    Mevordel
    Meticulus said:
    The only reason I want to do it is to see if I can get the rear cam working..;)


    Sent from my SAMSUNG-SGH-I577 using Tapatalk
    Click to expand...
    Click to collapse

    Makes sense. I believe Jackpot had hacked together a working lib/kernel combination on cm9 or cm10 once right before we got 3.0 working, but it has since been lost to the dungeons of time. My newer kernel is uploading now. I'm going to add hardware support piece by piece, first power management (rebooting), then eMMC, the FSA switch, then the screen and whatnot. I noticed though that a couple hundred lines of camera code was in mach-venturi.c, so maybe that is what needs to be updated.

    The latest work on the 2.6 kernel is at https://github.com/Mevordel/android_kernel_samsung_venturi_2.6 I believe, unless iurnait did some later work after I left. Koala888' had an unstable kernel, but I think it was just performance tweaks. The order of work was Entropy512 -> Ambrice -> JackpotClavin -> me -> iurnait.

    There's so much cruft in that tarball dump it's disgusting, though. IIRC, a diff of the vanilla 2.6.35.7 and what Samsung gave us is like 51 MiB! :gasp: And if you do go to their site, don't get the US one. That's for a never-released froyo version (2.6.32). Interestingly, we do get the source for their sound enhancements that made some people stay on 2.2.

    Edit: I can confirm the power/volume buttons do in fact work at the moment. Such an important part, I know. cat /dev/input/event1 :cowboy:

    Edit2: Upload is done https://github.com/smaeul/kernel_samsung_aries
    View
    2
    M
    Mevordel
    Meticulus said:
    If anyone wants to see what I've been working on for the YP-G70:

    https://github.com/Meticulus/slim_d...mmit/7ccd47c874f9a00c0397c8e8f17f3faaf72e256b

    Basically FULL- GAPPS.

    I was fracking frustrating, enlightening and fun! ;)

    EDIT: forgot a few lines - https://github.com/Meticulus/slim_d...mmit/6dd83396dcfa853119c840306fe8f10dbf142411
    Click to expand...
    Click to collapse

    Cool!

    Is binary blob lvm the normal way to do it? Seems kinda hacky to me, but whatever works.

    Following up on my kernel progress: I couldn't get UART or USB out of anything newer than 3.0, because our chip has no support past that (like the OMAP4/Galaxy Nexus). I didn't try very hard with the AOSP kernel/samsung (made for crespo), but the cyanogenmod aries kernel works with no modification. I'm going to build up a new kernel for us that we can hopefully upstream to aries so we don't have to maintain a separate one ourselves (or at least, anything but our device's part).

    To continue the discussion: I got my SGP in January 2012 from Newegg and promptly black-screen bricked it. So I sent it back and got a refurb off Amazon. I got a smartphone (GNex) that August, so I lent it to a family member. She got a smartphone last month, so I have my SGP back as purely a development device.
    View

New posts