Advertisment

Search

Monday, October 27, 2014

Introducing Build Server Beta

Hey guys, I decided that I needed to off load builds from my local computer so I got us a build server. It's currently in beta, I'm working to insure that it can reliably build by itself every day. While it is in beta you can expect so volatility.


  • I may need to reboot the server without warning and this may cut you off when downloading. Make sure to use a download manager that supports resume if you have a slow connection!
  • Changelogs may not be correct!
  • Server may be offline during the night. ( I'll always get it back on asap)
  • DAILYS ARE NOT TESTED! So do a backup before flashing one.

You can monitor the build server here: http://www.meticulus.co.vu/p/blog-page_25.html

Daily's are pushed to the Downloads page for each particular device.

Build Cycle starts at midnight CDT and are build in this order:

  1. venturi (Galaxy Player 5)
  2. codinalte ( Exhibit / Ace2e )
  3. m470 (Sero 7 Pro)
Please do not report issues about the build server at this time. Still working on it.

Wednesday, October 22, 2014

NEW BUILD!: Carbon for Galaxy Player 5


  1. Optimized memory in hardware OMX libs for Nutella MFC sizes.
    1. This should workout any video related issues.
  2. Increased NR buffers in the kernel
    1. Seems to have stabilized OC but lost 3-4 megs of system memory.
  3. Nutella Kernel Logo and localversion
  4. Y-Cable OTG (Not tested)
    1. Don't have Y-Cable but it merged pretty clean. If someone tries it please let me know
  5. Installation Compatibility Changes
    1. Carbon can now be flashed directly from any ROM with a custom recovery. (Even stock as long as you have a custom kernel with ClockworkMod)

NOTE: The installation procedure is way easier now but I have not updated the installation instructions yet. I don't think anyone will have any trouble.

Download in the download section as always.

Thursday, October 16, 2014

Wednesday, October 15, 2014

Saturday, October 11, 2014

NEW BUILD!: Carbon for Galaxy Exhibit / Ace 2e

This is a special release because I normally don't release this often but I got streaming video working and it fixes alot of video apps.

The new patch reportedly fixes Netflix, Crackle, and Twitch an may also fix other apps that stream video.

There may still be an issue with Facebook Messenger but with this latest patch, most video related apps should be working..


Download in the download section as always.

Tuesday, October 7, 2014

NEW BUILD!: Carbon for Galaxy Exhibit / Ace 2e


  1. Upstream Carbon updates
  2. Instagram (Fixed video upload)
  3. Fix FC at the end of video record.
Download in the download section as always..

Friday, October 3, 2014

NEW BUILD!: Carbon for Hisense Sero 7 Pro

  1. Carbon Upstream updates
  2. Add Sponsor section ( Thank you to all who have donated!)
  3. Offline Charger updates
    1. Sweep2Wake and DoubleTap2Wake
    2. Show date and time in charging mode.
    3. Allow don't suspend in charger.
Download in the download section as always.

Wednesday, October 1, 2014

NEW BUILD!: Carbon for Galaxy Player 5


  1. Carbon Upstream updates
  2. Add Sponsor section ( Thank you to all who have donated!)
  3. Offline Charger updates
    1. Sweep2Wake and DoubleTap2Wake
    2. Show date and time in charging mode.
    3. Allow don't suspend in charger.
Download in the download section as always.

NEW BUILD!: Carbon for Galaxy Exhibit / Ace 2e


  1. Carbon Upstream updates
  2. Add Sponsor section ( Thank you to all who have donated!)
  3. Offline Charger updates
    1. Sweep2Wake and DoubleTap2Wake
    2. Show date and time in charging mode.
    3. Allow don't suspend in charger.
Download in the download section as always.

About Instagram and Twitch video:

I looked at this problem for a long time. It's a very difficult problem to track but basically, our proprietary STE vendor blobs do not properly support certain OMX extensions such as "OMX.google.android.index.enableAndroidNativeBuffers2" which was actually implemented in android a long time ago. Now, we do have "leaked" source code but the code is not specifically for our device and is a nightmarish mess. So trying to using that source causes all sorts of build errors. It's only value, is to help give us an idea about what's going on in the proprietary blobs. I suspect that that this is going to be one of those problems that never gets fixed...

Sunday, September 28, 2014

3.0.101 Kernel for Galaxy Exhibit / Ace 2e (Testers wanted)

I patched up our 3.0.31 kernel to 3.0.101 and am testing it now. Everything seems to work OK but I did have a few hiccups the on the first couple boots. There was some "crash and soft reboot" on the first couple of boots but it seems to have resolved itself.

It seems to run fine but, everyone uses their device differently so I'm hoping some testers will try this out and let me know if anything is amiss.

I created the changes is a separate branch for testing here:
https://github.com/Meticulus/android_kernel_samsung_codina/tree/3.0.101

If you'd like to test:
  1. Download: https://www.androidfilehost.com/?fid=23681161096071155
  2. Replace you current kernel modules with the ones in the zip. (/system/lib/modules)
  3. Reboot to download mode
  4. Flash the kernel (.md5 file )with Odin. 
  5. If there seems to be some soft reboots, reboot the device a few times and see if it clears it self up.
  6. Let me know how it is...

Tuesday, September 23, 2014

NEW BUILD!: Carbon for Galaxy Exhibit \ Ace 2e




  1. Upstream Carbon updates
  2. Added DoubleTap2Wake
  3. Added Google DNS
  4. Youtube fixed, don't need H.264 softdec switch ( keeping it in, might need it in the future )
  5. Bluetooth fixes ( needs testing ) 
Download in the download section as always

Monday, September 22, 2014

NEW BUILD!: Carbon for Galaxy Player 5



  1. Upstream Carbon changes
  2. Added DoubleTap2wake
  3. Added Fast Charge 
  4. Added Google DNS ( known to interfere with tethering as a server)
  5. Reworked process spawning for CodinalteParts (much better memory and performance )

Download in the download section as always


NEW BUILD!: Carbon for Hisense Sero 7 Pro



  1. Upstream Carbon updates
  2. Fixed startup/reboot issues!!! (FINALLY!)
  3. Added DoubleTap2wake.
  4. Added Google DNS (Needs testing and known to interfere with tethering as server)
  5. Reworked process spawning in CodinalteParts ( much better memory usage and performance)
NOTE: Don't use auto logcat, auto kmsg, auto ril log. These need work for this device.

Download in the Downloads section as always

Saturday, September 13, 2014

NEW BUILD!: Carbon for Galaxy Exhibit / Ace 2e

































  1. Carbon upstream updates
  2. Integrated CodinalteParts (Settings -> Extras)
  3. Added SWEEP2WAKE!
  4. Added BLN and BLN Blink switches!
  5. Added h.264 workaround for Youtube
    1. NOTE: make sure to "clear" youtube app in recents before turning this on.
Download in the download section as always...

Thursday, September 11, 2014

NEW BUILD!: Carbon for Hisense Sero 7 Pro





  1.  Integrated Codinalte Parts
  2. Added Sweep2Wake
  3. Upstream Carbon Changes.
NOTE: I'm still trying to figure out the start up issues. There is an ANR in the systemui on startup and I think it has something to do with CM's new theme chooser...

Download in the download section as always.


Wednesday, September 10, 2014

NEW BUILD!: Carbon for Galaxy Player 5



  1. Integrated Codinlte parts into venturi.
  2. Added sweep2wake ( buttons also wake ) NOTE: uses wakelock!
  3. Bluetooth tether client workaround.
  4. Upstream Carbon changes.
Download in the downloads section as always.

Friday, August 29, 2014

NEW BUILD! PhilZ Touch Recovery for Galaxy Player 5

I spend some time making sure all the things that didn't work in the last build work on this one. AFAIK, everything is working.


  • Screen turns on and off properly now.
  • Touch functions working properly.
  • Virtual keys working properly.
  • Physical keys working properly.
  • Aroma file manager working.
  • Can flash this recovery in your current recovery.
  • Recovery persists even if you wipe cache.

Let me know if there are any issues.

Download in the download section as always

Thursday, August 28, 2014

Galaxy Player 5: Screen Recording Crashing after 60 sec[FIX]

A while back I noticed that I trouble creating screen captures that where more that 60 seconds long on the Galaxy Player 5. I like to take Screen Captures of the ROM to show case because  when I checkout a ROM I like to make sure it has the core features that I want. So when I create a ROM it's nice to show off the Settings area so people can see, before hand, if the ROM has a particular feature. During my testing I've notice that Screen Recording seems to crash after approximately 60 seconds and for the longest time I thought it was probably a "low memory" issue with this device. In the back of my mind though, I had a theory, that I always dismissed as unlikely but recently I tried it and it worked! This is how to get screen captures for more than 60 seconds:

The key is this line: https://github.com/Meticulus/android_device_samsung_venturi/blob/carbon/etc/media_profiles.xml#L92
where it says "duration=60". This file is on the device @ /system/etc/media_profiles.xml.

To change it to say... 12 minutes ( Don't know if there is any upper limit???)

  1. Make sure that /system is remounted rw.
  2. Open the file : /system/etc/media_profiles.xml
  3. Change the line :

<EncoderProfile quality="480p" fileFormat="mp4" duration="60"> 
to
<EncoderProfile quality="480p" fileFormat="mp4" duration="720"> 
Save and reboot.


Now you should be able to do screen recordings up to 12 minutes. Possibly camera video recording up to 12 minutes as well!

Cheers

Monday, August 25, 2014

NEW BUILD!: Carbon for Galaxy Exhibit / Ace 2e


I haven't had a clock freeze issue in a while but I've recently started to understand a little more about how the time system works in android so I put in a "Clock Freeze Monitor" to check for a potential issue that could cause the status bar clock to freeze.

  • Codinalte: added Clock Freeze Monitor
  • Carbon upstream changes.
  • Fixed apps to sd.
  • Lowered Font size of cLock widget so it doesn't look "cut off"
NOTE: From now on, builds will include the device's codename in the zip filename.

Download in the download section as always.

Sunday, August 17, 2014

EXPERIMENTAL BUILD:! Carbon for Galaxy Player 5

This is an experimental build because the magnetic sensor data is not correct. I just don't know enough about it to get it working properly.







  • Upstream updates from Carbon ( HOVER out Heads Up in)
  • Enabled lockscreen widgets.
  • Fixed CRT animations
  • Orientation sensor working.
  • Magnetic sensor is um... doing something.
  • Apps 2 sd enabled and working on external sdcard.

Tuesday, August 12, 2014

NEW BUILD!: Carbon for Hisense Sero 7 Pro


  • Upstream Carbon changes.
  • Restored cpu hotplug functionality.
Download in the download section as always.

Monday, August 11, 2014

NEW BUILD!: Carbon for Galaxy Exhibit / Ace 2 e

  • Just upstream changes from Carbon

Download in the download section as always.

EDIT: To fix "Apps to SD" download the following archive and put the 2 binaries in the "/system/bin" folder, replacing the existing ones

Fix-move-to-sd.zip

Sunday, August 3, 2014

Notes: Thinking About Codinalte Youtube Video Quality Issues

Quick personal note: I'm feeling much better these days but the long break has caused me to loose my development "mojo". I'm doing research as to how to get it back; apparently there was someone named Stella who lost her groove and she got that back. Then there is also Austin Powers; I guess someone took his mojo and he got it back as well... so need to watch/rewatch those I guess.

In the mean time, I've been thinking about a particular problem with Codinalte AKA: Galaxy Exhibit or Galaxy Ace2e. Well, this problem seems to exist across all codina/Galaxy S3 mini variants. In the official YouTube app, video quality is quite poor. No matter how you set the settings the quality settings the video just looks bad...

Now, Codinalte can play video in other contexts just fine. Video's look great in mx player and I think you can even use the browser and get better quality on the YouTube website so it does not seem to be a question of the device not being able to render good quality video; it obviously can and that leads me to believe that this is simply a misconfiguration somewhere.

Looking at the logs I found this:

E/YouTube (32655): apps.youtube.core.utils.a.e:131 Could not select a stream, defaulting to itag 36

Many of you may not know this but I worked on a video app a couple(?) years ago and at that time I was very familiar with how YouTube video's work. So when I saw the term "itag" I remembered that YouTube's web clients use to request a manifest of available qualities and encodings before selecting one to stream and each one had an "itag" number. Basically it's like this: The YouTube client would figure out what types of video's could be played i.e ( mp4, webm, mpeg, avi...). Then it would download a list of available encodings for a particular video. Then compare the list until there was a match and basically go with that. So, if the client could play mp4's and there is an mp4 available then we play that one. It was a little more sophisticated than that but you get the idea.

The above error seems to indicate that the YouTube app could not find a compatible stream in the list so it's defaulting to some "lowest common denominator"

ATM: I haven't found the spot where the android frameworks provide information to apps about what types of video can be decoded... Perhaps another dev will see this and get some insight...

EDIT: I have already tried to force Codinalte to use different decoders. With the recent inclusion of FFMPEG decoders, I thought this would be a good idea. I was able to verify that I was using different decoders but the result was still bad quality video. In all actuality no notice able change what so ever.

Comments welcome...

Thursday, July 31, 2014

NEW BUILD!: Carbon for Galaxy Player 5


  • Just upstream changes from Carbon

I'm hearing a lot of chatter about WiFi issues and I'm starting to think that INT Players might be having an issue with the WiFi driver I pulled in from CM crespo. Need to know, if it just INT Players or both or what... I am not having any issues with the driver...

Download in the download section as always...

Thursday, July 10, 2014

Still in Hospital but going to try to update...

Sorry for the lack of updates fella's, believe it or not, still in the hospital. I thought this would be a short thing and I'd be able to get right back to business but, that doesn't seem to be the case. I have already been here 10 days and I have gotten no indication that they are going to release me anytime soon so, I've decided to try and do updates from here. So be on the look for those.

Also I received a couple of donations in the past few weeks and it is my intention to create a sponsors section ( both in the ROM and on this site ) for the awesome people who donated money. I know that pulling out the pocket book to donate can be difficult. Thank you very much!

That being said, I will most likely not be working on my own code while I'm still in the hospital. I'm just going to try to maintain my current patches and update Carbon Code...

-Meticulus

Saturday, June 28, 2014

Sick fellas... No updates for a while..

I got a spider byte in a sensitive area. It's really messing me up, so I can't do updates for a while. Check back in when feeling better.

-Meticulus

Wednesday, June 25, 2014

NEW BUILD!: Carbon ROM for Hisense Sero 7 Pro


  1. 4.4.4
  2. Carbon upstream updates
  3. A2dp/Hdmi audio patch (Dopa) not tested
  4. Charging mode detection patch (Dopa)
  5. Miracast patch (Dopa) not tested
  6. Removed all init tunables... (Diagnostic... may be back in future build)
    1. Preliminary Notable Effects
      1. Cpu hot plugging disabled.
        1. All Cpu's on all the time.
        2. Min cpu 760Mhz can't be changed
        3. Performance seems awesome.
        4. Not sure about battery life yet...
  7. Smart dimmer disabled ( Is it just me, really annoying!? )
  8. Performance and Developer options enabled by default.
  9. New info in "About Carbon"
  10. Disabled "Update recovery on flash option"
  11. Probably for got a couple...

Download in the download section as always...

Monday, June 23, 2014

NEW BUILD!: Carbon ROM for Galaxy Exhibit / Ace 2e


  1. 4.4.4
  2. Upstream Carbon changes
  3. Removed CarbonDelta and ROMStats
  4. Lockscreen Notifications disabled by default
  5. Enforce Clean installs ( GApps must be reinstalled on every ROM flash)

Download in the download section as always.

NEW BUILD!: Carbon ROM for the Galaxy Player 5


  1. 4.4.4
  2. Carbon upstream updates
  3. Removed CarbonDelta and ROMStats
  4. New Wifi Driver from CM Crespo
  5. USB Tethering is back
  6. SDcard Swapping is back ( Not tested )
  7. Clean installs enforced (/system always wiped | must reinstall GApps every ROM flash )
    1. NOTE: You should still do a factory reset every time.

TIP: If the camera ever stop working, clearing data on the camera app will most likely fix it.

Download in the download section as always

Saturday, June 21, 2014

NEW BUILD!: Carbon ROM for Galaxy Exhibit / Ace 2e

I know it's been awhile, I've been working on other devices but this is my initial release of Carbon ROM for the Galaxy Exhibit / Ace 2e. As far as I can tell everything is functioning properly. Leave a comment down below if there are issues. I know that 4.4.4 has dropped but I have not updated my code base yet because I have been working on device specific issues.



Download in the download section as always...

Thursday, June 19, 2014

Galaxy Player 5: Experimental Wifi Driver

Recently, I started to notice just how "flaky" the wifi is on Venturi. Wifi issues can be tough to diagnose because there are so many "typical" things that can cause wifi issues. In addition to all the typical network connectivity issues that can arise, there are also the ones that are specific to wifi such as interference from microwaves ( ever try to get online while standing next to a microwave that's heating up your burrito? ). So when I read that people are having trouble with wifi on my ROM's I'm pretty skeptical but I finally took the time to take a really good look at wifi today and it does seem that while it does stay connected, that connection is quite sketchy.

There aren't really any errors to go by, things just sort of start timing out. It seems to be one of those sneaky intermittent issues that just really hard to nail down. I decided to swap out the wireless driver we have now and swap in the driver from CM crespo. I alot of ways Venturi is alot like crespo (Nexus S) and I assumed that there wifi driver should work for us and... it does! Since this is one of those obscure issues, it's going to take some time to test but I thought that you guys might want to check it out.


Download: bcmdhd_test.zip
  1. Back up your original driver file @ /system/lib/modules/bcmdhd.ko
  2. Replace it with the one in the zip file.
  3. Reboot.

NOTE: I've assume the .ko file is all that you need.

I'm told that the method above does not work so here is the kernel and all the modules.
Download: BCMDHD_WIFI_TEST.zip


  1. Do a full backup
  2. Install the kernel using heimdall or dd ( If you don't know how to do that then you should not be doing this anyways! )
  3. replace all the modules with the ones in the zip
  4. Reboot.
Or
  1. Wait for me to finished my own testing.
Leave a comment down below and let me know if this works better!


Tuesday, June 17, 2014

NEW BUILD!: Carbon ROM for Hisense Sero 7 Pro

Hey everyone, this is my initial release of Carbon ROM for the Hisense Sero 7 Pro. Should be operating much the same as the Beanstalk build. Leave a comment here if you find any issues and I'll look into it.




Download in the download section ( as always ).

Monday, June 16, 2014

NEW BUILD!: Carbon ROM for Galaxy Player 5

Hey guys this is my initial release of Carbon ROM, for the Galaxy Player 5. If  you coming from one of my Beanstalk builds, I think you'll find that most/all the features you loved in Beanstalk are in Carbon as well.

Issues:

  • USB Tether missing (Fixed next release)
  • Sdcard swapping missing (Fixed next release)

Screens:


Sunday, June 15, 2014

Beanstalk ROM: More Than I Can Chew...

Just a few days back I posted new repos for Beanstalk ROM just after my first successful build. I was thinking that I would be able to quickly get to a point where I could manageably update Beanstalk on a regular basis but this is looking less and less likely. The problem is the framworks_base repo. I've tried merging CM and AOSP but there were just way too many merge errors. I just do not have the skill to deal with that many merge errors and as time goes on, the frameworks_base repo will get further and further behind in code updates causing more and more issues. I never wanted to be the sole maintainer of a ROM. I'm really more interested in kernel development for the devices that I own. That's really where I want to focus my effort in developing my skills and trying to maintain this ROM is taking me away from my goals. It's a shame, I really like Beanstalk but it seems that it lives and dies with Scott.


My apologies to all, I know that it seems that this project was just starting to gain traction again but alas... For Galaxy Player 5, Galaxy Exhibit / Ace 2e,  and Hisense Sero 7 pro owners that were running my Beanstalk builds, I'm switching to Carbon ROM. I'll be running builds soon so keep an eye out for that.

P.S. If anyone would like to try their hand at it maintaining Beanstalk and have questions or need anything, let me know.


Thursday, June 12, 2014

NEW BUILD!: Beanstalk 4.4.300 for the Galaxy Player 5

This is a maintenance build to get up to 4.4.3. I have noticed a couple of minor issues:


  • In the google now launcher, google search crashes due to, what I believe is, an issue with the audio driver and "OK Google".
  • There seems to be a transparency issue with Icons on Nova Launcher???
  • The issue with screen not turning on after locked, FIXED
  • Button backlights FIXED
Please leave a comment down below if you have any other issues...

Download here

Wednesday, June 11, 2014

Beanstalk ROM New Repo's for DEVS

After battling through nightmarish build errors that through me for a loop more that once, I have Beanstalk ROM building and updated with the latest CM 4.4.3 code. If your not a developer but there is a developer for your device that builds Beanstalk ROM you might want to pass this along to them.



Notes for Developers:

I've built Beanstalk for on device and it was an extremely dirty build so, be prepared for issues to arise. I'm running a clean build today to shake out any left over problems. I initially had some device specific trouble with some sysfs paths from liblights but I don't think this was a Beanstalk problem, just a general problem with 4.4.3. In order to fix it I had to set user permissions on the backlight and button backlight brightness paths. Just a heads up. Also, there have been changes in 4.4.3 to use libexif instead of/ or in addition to libjhead. I had a few issues with that as well and in order to fix the build, I had to manually build libjhead. Hopefully, I'll be able to spot a place to fix that soon. That is, if it's not already fixed by doing a clean build.

Want to join the Beanstalk Team?

If you'd like to help me maintain these repo's get a hold of me on Google+ or send me a pm on XDA. Please include info on your work so I know you have the requisite skills.

Got a fix?

Please submit pull requests for anything that you have fixed and I also willing to merge in device specific code as long as it's properly isolated and won't break the build for other devices. Let me know if I need to fork a repo that isn't already forked.

Updating your repos:

Rather than re-syncing all of the repos, I was able, while I was working, to update my code base from what I already had ( Scott's repos ). All I had to do was reinitialize the repos in my working directory by following the normal instructions but now with an updated url.

New Repo's


Initialization Repo


Problems?

Leave a comment down below and I'll check it out...

Stay tuned to this blog for updates and developments on Beanstalk ROM


Sunday, June 8, 2014

The Future of Beanstalk ROM

As you most of you know, the creator of Beanstalk ROM, Scott Hart, has not been updating Beanstalk for the past month or so. I noticed early but assumed that Scott had his reasons. I thought that maybe he was taking a break or perhaps waiting for the next version of Android (4.4.3) to drop. Well, it turns out that this is not the case. I spoke to Scott briefly yesterday and I although I won't go into the details of his personal life, suffice it to say that I got no indication that he would not be updating Beanstalk anytime soon.

Because I like Beanstalk so much, I've decided to attempt to bring Beanstalk up to date. However, I'm not sure my skills are up to the task. There are so many things, about the way Scott was maintaining Beanstalk that I don't know/understand, and that's making the process very difficult. So, I'm not sure if I can get Beanstalk up to speed with 4.4.3. I will continue to try as long as I can make progress and I don't get "stuck".

P.S. If you like Beanstalk, head on over to the Facebook page here and give Scott your "Best Wishes"

-Future Uncertain
--Meticulus

Wednesday, June 4, 2014

NEW BUILD: Beanstalk 4.4+ for the Galaxy Player 5

  1. Increased System Memory from 412 -> 450. ( Stole from OMX, Please leave a comment here if you have video playback issues. I have not had any but I haven't tried every format and every quality..)
  2. DID NOT include new sensor changes because I still don't have the magnetic conversion values worked out. The values are just way off.




Download here

Tuesday, June 3, 2014

Balancing Battery Life and Memory on the Galaxy Player 5 on Beanstalk 4.4+

Venturi is a low ram legacy device. Let's face it, it's old. Don't get me wrong, I love the device but going forward it's going to be more and more difficult to get good performance and the Android OS grows; Difficult but not impossible. One of the most challenging performance bottlenecks is RAM. We only have 512Mb, In the next release for the YP-G70, I've increased the available system RAM to 451Mb by stealing some ram back from OMX. OMX is responsible for encoding and decoding audio and video. As a result we are losing "Hardware" support for rendering HD video. Actually, Venturi could only render 720p video anyway and we can still render HD video using "Software" decoders. Personally I use MX Player and you only need to select the "SW" decoder and video renders great. I personally think it's an excellent trade off.

Another way to insure a good balance between battery life and available memory is to manage your "minimum free memory" options in "Settings -> Performance -> Memory Settings".

There are 4 presets:
  1. Very Light
  2. Light
  3. Medium
  4. Aggressive
  5. Very Aggressive


"Very Aggressive" tries to keep the most free memory. When it detects that the amount of free memory is less than what you specified then the "Low Memory Killer"(LMK) goes through the list of processes that are running and kills any of them that it can until the specified amount memory is free. You might think that is going to be the best option but not necessarily so; That option may cause LMK to be constantly working to free memory even when you are not doing anything. I suspect that when some apps are killed, they get automatically re-launched. So LMK is eating your battery by constantly killing apps.

You can observe this behaviour running the following commands in the terminal emulator or adb:
su
cat /proc/kmsg
You will see message like the following:
select 14561 (android.vending), adj 15, size 11020, to kill
send sigkill to 14561 (android.vending), adj 15, size 11020
Every time you see those messages, it's LMK trying to free memory to satisfy the request of  keeping "minimum free memory". It's OK to see it occasionally but if  it's happening all the time, the "minimum free memory" setting is too high and you try lowering it.

I usually float between Aggressive and Normal.

How to Build Beanstalk 4.4+ ROM for the Hisense Sero 7 Pro

How To Build

Step 1: Setting up the Build Environment.

You'll need Linux to be able to build Beanstalk. You have three choices here; you can:
  1. Install Linux natively on your computer.
  2. Dual boot Linux and Windows.
  3. Use virtual machine software ( virtual box, vmware ) to run linux.
NOTE: I recommend you use Ubuntu 12.04 LTS to build. That's what I use.
NOTE: When I say "read", I mean read and comprehend.
NOTE: Read through the topics here as well: http://wiki.cyanogenmod.org/w/Development

Step 2: Downloading the Source.

NOTE: Some say that it is better to download the ROM source and put in your local manifest later. I don't know if that's best but that's what we are going to do.
BEFORE YOU BEGIN: You are about to start downloading 5 - 15 Gigs of data. That could take a very long time, so plan accordingly. I like to start juts before I go to sleep and let it go overnight! If you have to work, perhaps start it before work and let it go through out the day.
Execute the following commands in a linux terminal:
mkdir /home/$USER/BS
cd /home/$USER/BS
repo init -u git://github.com/scotthartbti/android.git -b kk44
repo sync
WARNING: There may be times, towards the end when it seem like, the download is stuck and not making any progress because there are no updates on the screen. BE PATIENT!, open a program that will show how much bandwidth you are using to be sure!
NOTE: Steps 3 and 4 are from Scott's repo here: https://github.com/scotthartbti/android/tree/kk44.

Step 3: Set up local manifest.

The local manifest is different for every device. It contains those repos that are device specific, where as the ROM code you just "repo sync'd" is code that is general to any device.
Execute the following commands in a linux terminal:
gedit /home/$USER/BS/.repo/local_manifests/sero7pro.xml
Now copy the following into sero7pro.xml, save and close.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="Meticulus/beanstalk_device_hisense_m470" path="device/hisense/m470" remote="github" revision="kk44"/>
  <project name="Meticulus/beanstalk_hisense_m470" path="kernel/hisense/m470" remote="github" revision="kk44"/>
  <project name="Meticulus/android_vendor_hisense" path="vendor/hisense" remote="github" revision="kk44"/>
  <project name="Cyanogenmod/android_system_bluetooth" path="system/bluetooth" remote="github" revision="cm-10.2"/>
</manifest>
Execute the following commands in a linux terminal:
cd /home/$USER/BS
repo sync
NOTE: Yes we are syncing again and No, it shouldn't take quite as long. Every time you repo sync just new data is downloaded. So we are downloading the 4 repo's we just put in and any updates that may have occured to the repo's we already have.

Step 4: Building

NOTE: Now you have everything that you need to build Beanstalk for your Hisense Sero 7 Pro. Build times depend on you PC performance specifications. In the following terminal command "-j8" represents the number of concurrent tasks to execute. For low specs machines (such as mine) lowering the value to "-j3" may help speed things up. For high spec'd machines raising the value may speed things up.
NOTE: It may take anywhere from 5 hours to 15 hours depending on system specs for a complete build. Execute the following commands in a linux terminal:
cd /home/$USER/BS
. build/envsetup.sh
lunch cm_m470-userdebug
make -j8 otapackage
WARNING: There may be times, towards the end when it seem like, the build is stuck because of a lack of updates on the screen. BE PATIENT! libwebviewchromium.so is a beast and is usually the last file to be build. It takes awhile to complete. I ususally have 15 to 20 minutes of "no screen activity" before it finally finishes building that lib and then continues...

Monday, June 2, 2014

NEW BUILD: Beanstalk 4.4+ For Hisense Sero 7 Pro

This is my initial release of Beanstalk 4.4+ for the Hisense Sero 7 Pro. As far as I can tell all the core functionality is working but I have not tested every little thing. Please report any issue you have!

Download here

Galaxy Player 5: How to Change your MAC address

I recently wrote some code that taught me a lot about how wifi mac address work in the Android world. I suspect that most people are not aware that they can change their mac address to whatever they want. So I thought I'd write some simple instructions on how to do it for the Galaxy Player 5.

Prerequisites


  1. Good file manager app. ( I use ROM Toolbox )
  2. Good text editor app. ( I use ROM Toolbox )
  3. Make sure that /system is writeable. You may need to manually remount system rw:
    1. In terminal app: 
      1. su
      2. mount -o remount,rw /system
    2. Using ADB
      1. adb root
      2. adb remount


If you're on a recent KitKat build, such as Beanstalk 4.4+ then:


  1. Use the file manager to browse to the file /efs/imei/.nvmac.info and open it with a text editor.
  2. Inside you will find your mac address, change it to any valid mach address you like.
  3. Save
  4. Reboot.


If you're on an old KitKat build or an older incarnation of Android then:

  1. Use the file manager to browse to the file /system/vendor/firmware/nvram_net.txt and open it with a text editor.
  2. Scroll down till you see a line that starts with macaddr=
  3. What follows is your wifi mac, change it to any valid mac address.
  4. Save.
  5. Reboot.

Sunday, June 1, 2014

How to Build Beanstalk 4.4+ ROM for the Galaxy Player 5

How To Build

Step 1: Setting up the Build Environment.

You'll need Linux to be able to build Beanstalk. You have three choices here; you can:
  1. Install Linux natively on your computer.
  2. Dual boot Linux and Windows.
  3. Use virtual machine software ( virtual box, vmware ) to run linux.
NOTE: I recommend you use Ubuntu 12.04 LTS to build. That's what I use.
NOTE: When I say "read", I mean read and comprehend.
NOTE: Read through the topics here as well: http://wiki.cyanogenmod.org/w/Development

Step 2: Downloading the Source.

NOTE: Some say that it is better to download the ROM source and put in your local manifest later. I don't know if that's best but that's what we are going to do.
BEFORE YOU BEGIN: You are about to start downloading 5 - 15 Gigs of data. That could take a very long time, so plan accordingly. I like to start juts before I go to sleep and let it go overnight! If you have to work, perhaps start it before work and let it go through out the day.
Execute the following commands in a linux terminal:
mkdir /home/$USER/BS
cd /home/$USER/BS
repo init -u git://github.com/scotthartbti/android.git -b kk44
repo sync
WARNING: There may be times, towards the end when it seem like, the download is stuck and not making any progress because there are no updates on the screen. BE PATIENT!, open a program that will show how much bandwidth you are using to be sure!
NOTE: Steps 3 and 4 are from Scott's repo here: https://github.com/scotthartbti/android/tree/kk44.

Step 3: Set up local manifest.

The local manifest is different for every device. It contains those repos that are device specific, where as the ROM code you just "repo sync'd" is code that is general to any device.
Execute the following commands in a linux terminal:
gedit /home/$USER/BS/.repo/local_manifests/venturi.xml
Now copy the following into venturi.xml, save and close.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="Meticulus/beanstalk_device_samsung_venturi" path="device/samsung/venturi" remote="github" revision="kk44"/>
  <project name="Meticulus/nutella_samsung_venturi" path="kernel/samsung/venturi" remote="github" revision="master"/>
  <project name="Meticulus/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0"/>
  <project name="Meticulus/android_vendor_samsung_venturi" path="vendor/samsung/venturi" remote="github" revision="cm-11.0"/>
</manifest>
Execute the following commands in a linux terminal:
cd /home/$USER/BS
repo sync
NOTE: Yes we are syncing again and No, it shouldn't take quite as long. Every time you repo sync just new data is downloaded. So we are downloading the 4 repo's we just put in and any updates that may have occured to the repo's we already have.

Step 4: Building

NOTE: Now you have everything that you need to build Beastalk for your Galaxy Player 5. Build times depend on you PC performance specifications. In the following terminal command "-j8" represents the number of concurrent tasks to execute. For low specs machines (such as mine) lowering the value to "-j3" may help speed things up. For high spec'd machines raising the value may speed things up.
NOTE: It may take anywhere from 5 hours to 15 hours depending on system specs for a complete build. Execute the following commands in a linux terminal:
cd /home/$USER/BS
. build/envsetup.sh
lunch cm_venturi-userdebug
make -j8 otapackage
WARNING: There may be times, towards the end when it seem like, the build is stuck because of a lack of updates on the screen. BE PATIENT! libwebviewchromium.so is a beast and is usually the last file to be build. It takes awhile to complete. I ususally have 15 to 20 minutes of "no screen activity" before it finally finishes building that lib and then continues...