Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About boogyboo

  • Rank

Recent Profile Visitors

662 profile views
  1. I've got the current ubuntu android source repo as i have been working on porting it to my moto xoom tablet, but there are some serious limitations for "non-supported" devices. touchscreen implementation is a little different in ubuntu touch and requires some kernel modifications, and procedures for getting sensors to operate is still experimental at best and virtually impossible for most devices at this point. just from the trouble i'm having with getting it working on my xoom, i'm going to say it would be less than worthwhile to even attempt it for the open-c--though the open-c already has a working 4.4 status, which the latest ubuntu touch underlying system is based on 4.3 so it is possible feat. ubuntu touch is really only a viable options though when there are several people working together on development and when said device is a tablet. ubuntu touch on is not something that interests me at all on a phone. you could always download the source and try yourself :-)
  2. it won't show 3G instead it will display H or H+ (for HSPA) which is better than 3G anyway. there are also APN settings that will need to be tweaked to carrier specific values as the config file provided a catch-all file and may or may not be correct. the values for my carrier where not right and had to be slightly modded. this is not a rom fault but a user fault...
  3. here is where you are wrong, again. i had cm10.2 (4.3) [the one place you are right--typo btw, i've been around the block and your xda fanboy wanna be crap doesn't fly with me] running right off the bat when i got the device. it was the very first thing built. it ran just fine using the kernel from the 1.3 b2g repo which is what shipped with the american ebay open-c and was built from android 4.3, which is the same as your uk i believe. that kernel will boot cm10.2. but that kernel also didn't have config enabled in proc/config.gz for the config that ran b2g so the proper config had to be pulled from the config folder and slightly tweaked. i could not however get cm11 booting with that same kernel and config for whatever reason--which i'm sure was only config options related and not drivers because they ran fine in b2g. get over yourself. cause you ain't shizz
  4. cm10 can be built and booted using the kernel source that was used in the b2g 1.3 repo--anyone familiar with building would know this since 1.3 was based on jelly bean. it was the first thing i built for the phone back in september. i no longer have the cm10 repo on my machine though, and i scrapped those early builds. currently the cm10 repo will not complete syncing because of some whiny loser requesting dmca takedowns for code used to build pico tts included in android_external_svox until this is resolved i won't be able to re-build cm10. there's not really a big difference from cm10 to cm11 anyway. the main difference and thing that cm10 does better than 11 is the dialer and contacts--which is reason enough to want it. if i can dig up one of those builds on machine somewhere i'll shoot you a link
  5. Konstat is a whiny biotch. what a faggot

  6. i don't read your responses, you arrogant fanboy.
  7. rom info and link have been updated v2.1
  8. If you want to sticky it you can. it might be easier to find for everyone if it was. you can change the format if needed. a new link will be added here in a few hours along with updated rom info, so if you want to wait until that is done that would be great. thanks.
  9. last build has a severe battery drain issue that is caused by some garbage in the Cyanogenmod repo. new build is in progress and new link will be posted soon along with updated rom info and battery drain fix.
  10. boogyboo

    Cyanogenmod for ZTE roamer

    cm for the zte roamer sucked... i'm the dev who made it possible in fact, if talking about the zte roamer (avail / merit z990) try this aosp build of mine here: http://androidforums.com/threads/rom-stayboogy-aosp-roamer-v1-3-gps-working.853988/ i have since ceased development for the device for now... someone else released a 4.0.4 rom based off my work, but i'm positive they didn't fix the kernel so i wouldn't suggest it if i were using the device and wanted quality phone service...
  11. 1. you're obviously so eaten with jealousy that you can't see that my commits were on the cm11.0 branch. learn to look before you mouth off. so high and mighty trying to be correct--except you're wrong, totally wrong yet again... see attached photos, open your eyes... aside from that, the only reason i did what i did was for all your freaking crying and whinning like a little baby... which didn't stop but only got worse--imagine that. what are you 12 years old??? 2. you're no one and nothing. just a punk with a big mouth. so what? you're a "king" at modaco which doesn't mean jack squat in the real world. why keep running your mouth? makes you look even weaker in my eyes and shows how immature you really are. you're EVERYTHING that is wrong with the community and your constant crying proves it 3. you're wrong about performance settings--they did not stick in your build. cpu speeds, especially scaling_min_frequency would not stick and would revert to the low setting in the post boot script after a few moments. just because you didn't notice doesn't mean it's not true--but it is true. that's why i scrapped the script which i don't have to explain to some butthurt little crying baby konstat... instead of being an ass, maybe just leave my thread. you're not welcome with your whinning and garbage cluttering up the thread so you can ACT like you're something special...
  13. what is your deal? delusions of grandeur much? lol :blink: i understand overlays... all i did was use the original framework file and insert your values and changed a few others. i always start with the config.xml values.xml from the source and edit as needed. there's more than one way to do it... or do you not understand that? secondly, i have no reason to add to your git, as your device tree is just fine--i've complimented you on your work already, hell using your source to do my own build should be compliment enough as that's why you posted it, just like me. i just tweaked a few things to my own liking. i could have removed a few other things but chose not to. a few of the .sh files in /system/etc/ are not used at all and are erroneous. also init.target.rc is commented out in init.qcom.rc, which i know why that is, but zram swap is set in that file and so are the proper execution nodes in /dev for the proximity/light sensor on those devices with a proximity sensor. i added this to the init.rc included in the system source that gets copied over the root. i still do not understand what your deal is... i've also since changed a few more things that have not been added to my git since this, as well as played with the kernel some. the openc device tree on my github is useless lol. it won't build that way without changing the source a little and those who are using your builds won't be able to install it since it has assertions in the update script... this is far from my first build from source, dude... peace
  14. STAYBOOGY'S ZTE KIS3 KK 4.4.4 [CM11] v2.1 The last build had an extreme battery drain issue which I never could really narrow down in the Cyanogenmod source but it is definitely something that was added between November and January to the source (which they often add garbage on a regular basis since so many clueless people contribute to the code), so I reverted to an old edition of the repo which has completely fixed the issue. Great battery life in the 2.1 version By executive decision NavBar + Hardware keys are enabled by default--in my opinion this is the best setup for the device. I have also opted to not enable KeyDisabler which provides the option to enable either NavBar or the Hardware keys (while disabling the other completely)--mainly because it's a stupid idea and garbage code that has been added by the Cyanogenmod team If you do not like this and wish to have only the Hardware keys, add this to your build.prop and reboot: qemu.hw.mainkeys=1 To revert after doing so either delete the line from the build.prop or change 1 to 0 and reboot. Swap is no longer used--in fact it is not used in any of the Kis3 posted roms (from what I've investigated). If you run mount from the terminal you will see that the swapfile is never listed. Therefore, it has been removed permanently. If it was actually being used it would be listed by the mount command, and it would cause unwanted battery drain. CPU Settings actually stick and do not revert to userspace governor and 300Mhz scaling min frequency--set them how you want them CyanogenMod statistics, account, and setup have been removed as they are unneccessary for unsupported devices Performance Settings and Developer Settings are enabled and visible by default on the first boot--no more tapping nonsense No nag screen when adjusting cpu frequencies either Partition info added to settings menu since it is useful System apps put their dalvik-cache on the /cache partition by default; User apps will still use /data partition ROM is the fastest and most responsive of all available in my opinion. It is mostly CM11, just with more device appropriate settings. http://www.mediafire.com/download/wgg16g2rx0m2asz/stayboogy--zte-kis3--cm11--two-one--new.zip same directions for installing as the other roms SOURCES: https://github.com/stayboogy/stayboogy_kk_kis3 (contains all necessary minus the Cyanogenmod repo) ENJOY!!!
  15. so, i just hooked the phone to my service using the most recent of your builds and so far, no major complaints. good job. i've got hspa+ so it's using the best connectivity. i have the english standard open c that was sold by zteusa on ebay. the only thing negative i have to say is that there really needs to be some overlay work done in the device tree, so that's exactly what i'm doing in the source right now to perfect the build for my daily use. i appreciate all your hard work.

Important Information

By using this site, you agree to our Terms of Use.