[ROM][4.1.2][YP-G70][Feb18]CyanogenMod 10.0 Nightlies

Search This thread

JeonZiro

Senior Member
Sep 4, 2012
55
2
New York
Have you tried rebooting? Somebody else said they didn't work until then.



I'll remove that option from the menu as it's not going to work. What do you mean about Entropy's kernel? This ROM does not use his kernel, although it is based on it. When you install, it overwrites the previous kernel. See https://github.com/Mevordel/android_kernel_samsung_venturi/commits/jellybean



If nobody complains, I will remove them soon.

I ask because of the issue discussed previously with charging from a PC, and the charge time if that makes any sense. I don't mind it charging faster then when I first brought my galaxy, but it lasted me a strong two days without charge. Most ROMS i've tried after using that kernel only gives me about 5 hours of use (if i use it or not)

Honestly I'm not trying to argue, I didn't know it over-rides the kernel. Thank you for explaining this to me, this rom is worth it so I won't complain.
 
Last edited:

Mevordel

Senior Member
Apr 24, 2012
925
1,009
I ask because of the issue discussed previously with charging from a PC, and the charge time if that makes any sense. I don't mind it charging faster then when I first brought my galaxy, but it lasted me a strong two days without charge. Most ROMS i've tried after using that kernel only gives me about 5 hours of use (if i use it or not)

Honestly I'm not trying to argue, I didn't know it over-rides the kernel. Thank you for explaining this to me, this rom is worth it so I won't complain.

No worries. I will say, however, that this ROM will probably have higher battery usage due to the fancy new graphical effects and project butter increasing your CPU frequency. And of course overclocking will hurt battery life.

Give me a minute and I'll attach a zImage without the charging hacks.

Edit: here you go. Enjoy!
 

Attachments

  • zImage.tar
    4.9 MB · Views: 19
Last edited:
  • Like
Reactions: JeonZiro

JeonZiro

Senior Member
Sep 4, 2012
55
2
New York
No worries. I will say, however, that this ROM will probably have higher battery usage due to the fancy new graphical effects and project butter increasing your CPU frequency. And of course overclocking will hurt battery life.

Give me a minute and I'll attach a zImage without the charging hacks.

Thank you!! :victory:
 

DZonikg

Senior Member
Apr 11, 2012
802
218
Kragujevac
Any luck finding a different gapps package Mevordel?:)

Sent From my USA Galaxy Player 5.0

You have google 2 so can search for different google apps..but i thing it can only be removed google play from gapps and then install from market..just need to now which files are for google now

Sent from my Nexus 7 using xda app-developers app
 

DZonikg

Senior Member
Apr 11, 2012
802
218
Kragujevac
There's nothing really I can do about that. Are you sure it's not because of a corrupted media file?
I have zilion files on sdcard ..who can nou which are corrupt but puting .nomedia file in root of both sdcard removed the problem..and get me 1.8gb more space which .thumbnails folder growed.



Sent from my Nexus 7 using xda app-developers app
Did try re-booting but still my touch buttons don't work. However they light up when I touch the screen.
---------- Post added at 06:34 PM ---------- Previous post was at 06:19 PM ----------

They dont work for international..need a change in kernel

Sent from my Nexus 7 using xda app-developers app
 

EcHoFiiVe

Senior Member
Jan 29, 2012
1,575
737
Mundelein. IL
I go to sleep for six hours guys. Six. And I said: Don't let development go until I wake up. And this is the first thing I come to when I get up. You are all grounded. No Linux, no android and no XDA.


Mevordel I love you.

Sent from my MB886 using xda app-developers app
 

KOala888

Senior Member
Nov 21, 2010
821
292
Gdańsk
Any speed tweaks on JB CM10 is useless.

Sent from my Nexus 7 using xda app-developers app

maybe I used inappopriate name.
But increasing gaming performance and changing frequencies would result in only adventages. I meant same kernel improvements as on nexus s.

Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
 

mr32

Senior Member
May 17, 2012
110
43
Eindhoven
A tip: changing the density with LCD density modder did not work for me, it results in a bootloop with the following logcat error:
Code:
E/SurfaceFlinger(  332): ro.sf.lcd_density must be defined as a build property
Changing it directly in build.prop works in this case better
 

Karim.younus

Senior Member
Jun 12, 2012
228
19
Duns, Borders
Poor Medorval is being asked so many questions, lol. I can wait for the touch buttons as long as I can operate we're good.
 
Last edited:

DZonikg

Senior Member
Apr 11, 2012
802
218
Kragujevac
Originally Posted by DZonikg<br />
Any speed tweaks on JB CM10 is useless.<br />
<br />
Sent from my Nexus 7 using xda app-developers app
<br />
<br />
maybe I used inappopriate name. <br />
But increasing gaming performance and changing frequencies would result in only adventages. I meant same kernel improvements as on nexus s.<br />
<br />
Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
Use tegrack overclock ultmate..i can cofirm that it works on this kernel.

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

KOala888

Senior Member
Nov 21, 2010
821
292
Gdańsk
the tricky think is that in games gpu is rather more important than cpu. It can be overclocked by adding liveoc module to kernel or hardcodng it.

tegrak overclok is more workaround than a solution. I have no idea why you are so negative with having more jb kernels than one, or to have one better.

Nexus s developers have serious expirience and their changes are used on many devices, also those improvements are being implemented from a long time so they are tested and you can trust them :)

Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
 

Top Liked Posts

  • There are no posts matching your filters.
  • 69
    Note: Please upgrade to CM10.1 for some fixes. This is currently unmaintained.​

    Broken:
    • Bluetooth (some progress has been made, but it still does not turn on)
    • Camera preview, some JPEG corruption
    • Earpiece (sound comes out the speaker by the camera on the back instead)
    • Only earphones with 4-part plugs work (like those with a mic) the first time (see last "What if?" question)

    Installation:
    1. Reboot to CWM
    2. Make a Nandroid (optional, but recommended)
    3. Format /system if you had a different GApps package installed
    4. Install ROM
    5. Install GAPPS if you just formatted /system
    6. Wipe data/factory reset if you are coming from Gingerbread
    7. Reboot
    8. ??? (wait a while...)
    9. Profit

    What If....
    • I get a message saying "assert failed. Installation aborted"? Go to "Mounts and Storage" -> "Format /system" and try again.
    • my capacitive buttons don't work (US)? Reboot.
    • my capacitive buttons don't work (INTL)? Flash the international kernel.
    • the navigation bar is really annoying? See tweaks in second post.
    • the torch doesn't work? It's because camera is kinda broken. Workaround: take a picture with flash set to "on", and stay in the camera app.
    • I wiped data before flashing? It won't make a difference.
    • I can't update Google Now? Use the newer Google Apps package.
    • I want to switch my storage? See second post.
    • the ROM is too slow? Try enabling the overclock, or switch to ondemand governor, or use Mercurius kerne.
    • I can't get any headphones to work? Install SoundAbout and set it to wired with mic.

    Links:
    Development Thread
    Device and Kernel Source (Jellybean branches)

    Special Thanks:
    • The CyanogenMod team - for CM10
    • JackpotClavin - for getting us started and doing the real kernel work
    • Supermaster34 - for work on Bluetooth
    • DZonikg - for getting audio and camera to work
    • Koala888 - for doing the overclock and kernel speed tweaks
    • Everyone who tested the alphas
    • International users who helped to fix buttons
    • Those who encouraged me to JTAG my bricked player
    • Users! without them, I would be wasting my time. You make it worthwhile.
    48
    Downloads
    So the latest version was broken. My advice is just wait for CM10.1. To fix app installation issues on 2/18, stick the apps in /data or /system with a root browser first, or use the next oldest or Mercurius kernel.
    02/18 - http://www.mediafire.com/?o5e72z7sdopbja5 - Updated CM10 code
    01/22 - http://www.mediafire.com/?w7r2we0e4as90fs - Updated CM10 code, kernel RAM/OC tweaks, back cam fixed, .android_secure fixed
    01/08 - http://www.mediafire.com/?kbjsv6en7awa37d - Max OC set to 1.3 GHz, governor and touchscreen tweaked, newest CM10 code
    01/06 - http://www.mediafire.com/?h9yhna89wtjkb1s - Kernel OC'd + optimized, better camera HAL, remove useless libs, include Live wallpapers and extra sounds
    01/05 - http://www.mediafire.com/?7364sa929z4ycf7 - Fixed video playback and recording, updated CM10 codebase, remove seeder
    01/04 - http://www.mediafire.com/?dqhmm1jhoxlv2dc - Enable mass storage, fix vold for the last time, include rngd, new governor and scheduler
    01/03 - http://www.mediafire.com/?zjixb6ny435m2ss - Added MMS, tweaked storage and framework, improve camera
    01/02 - http://www.mediafire.com/?iz68q06041l628j - Initial Beta

    Alternate Kernels - You can replace the boot.img in the zip with one of these, flash it with heimdall, or rename it to zImage, stick it in a tar, and flash with Odin.
    International - Up to date - http://www.mediafire.com/?3mcbbwbv87h06af - For users with a physical home button. It will fix your capacitive buttons. This also has the driver for the Korean camera.
    No Charging Hack - Old - http://www.mediafire.com/?66cr74eey94i4ag - For those who prefer the stock charging algorithm, a USA boot image without charging hacks.

    Google Apps
    http://www.mediafire.com/?e8wuqk72997ucbg
    The normal GAPPS package will not fit on our /system. Use this one. Everything that is not included is available in the Play Store.

    Mods/Hacks
    There are 4 things you can edit in build.prop. If you want, you can edit the file before flashing. Here is what the defaults look like:
    Code:
    #########################################
    ## You can tweak the next 4 properties ##
    #########################################
    
    # Uncomment to switch internal and external storage
    [B]# That means remove the "#" at the beginning of the next line[/B]
    # ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
    
    # Change to 0 to enable softkeys, 1 to disable
    qemu.hw.mainkeys=0
    
    # Defaults to Mass Storage. You can change to mtp
    persist.sys.usb.config=mass_storage
    
    # LCD density (240 is default)
    ro.sf.lcd_density=240
    26
    Mevordel and I were actually working together on CM10.1 before he gave away his device but kept it private because we didn't know how far along we would make it with porting CM10.1 and didn't want everybody anticipated for something that might not happen.

    At any rate, I've been working on the 3.0 kernel for the last week or so. I'm using the Aries devices' kernel as a base and porting the Galaxy Player 5 stuff over the correct way, and not with hacks and stuff from the last time I tried the 3.0 kernel a few months back; so I started fresh and one feature after another came along. A few minutes ago I just got the sound working (remember how it was really sped up the last time I tried the 3.0 kernel??) It's fixed now; and it's pretty nice. As for where I am with this, the cameras still aren't working, but I think that's a library issue; not a kernel one. I'm gonna try to remake our device tree as close to the Aries and NexusS devices because they're really far ahead of us in terms of development. Right now, I believe a NexusS or any of the Aries devices' ROMs will boot on our devices with my kernel as long as you modify the .zip to install to our /system partition.

    What works with the kernel so far is:

    2-22: Got it booting + USB (just a black screen)
    2-23: Display, internal AND external sdcard support (it didn't work the last time I tried the 3.0 kernel), touchscreen
    2-24: Converted initramfs over to CM (recovery support, etc..) Thanks Ambrice
    2-25: Merged to 3.0.31 (it was 3.0.8) Fixed RAM 412 MB free on boot, battery driver,
    2-26: Non-working camera
    2-27: Fixed rebooting and powering off
    2-28: Basic sound support (didn't work however, got it working later on)
    3-12: Fixed hwcomposer (should be a lot smoother)
    3-14: Fixed video playback (Netflix works, as well as 1080)
    3-15: 3.0 USB files (I initially used 2.6.35.7 but now we use the latest)
    3-17: Vibrator, overclock (1.2 ghz), merged up to 3.0.68
    3-18: Sensors (accelerometer, compass)
    3-22: Working sound

    http://imgur.com/a0N04qg

    I'll try to be adding more features throughout the week as well as working on the device tree
    21
    Ok everyone. I am uploading one last nightly. I have given my player away and will not be able to test new ROMs, so I can't do much more than help with questions. It has been a great year of development and involvement with our small but active community (almost exactly that long), and I truly hope that these devices keep getting better and stay unbricked. :cowboy: Yes, I can't help but pop in every so often, but I will not be updating either this or Chip (unless this last build is horribly broken or something).

    P.S. Although I am not allowed to give details, rest assured that development for our device has far from stopped.

    Edit: Int'l is up. US is building.
    Edit2: Both are up!
    15
    A new build should come some time next week. KOala888 is working on the kernel, and once he is done, I will see if I can work on the camera issues and audio routing. Just so nobody thinks I've left or anything. ;)