Search results

Well, this was obviously not updated in a while... I don't have much time to work on this nowadays, and anyways there's arco's work , so this is officially discontinued. Good luck to everyone with their projects, and have a good day!

well yes, it's still under very slow development.. though i don't have much time to work on this. i did fix some things, then i stumbled into an annoying bug which took me ages to fix. now i dunno if there's still a point to this with everyone releasing cm10's for the wonder nowadays (including...

well, some of it may not work, but the code is there and there are working improvements. vsync may not be updated in this kernel, but triple buffering is, and project butter also uses that. other features of the "project" - anticipating events and bumping up cpu frequency, systracing system...

happy birthday! and about the project butter question - it's just a codename for many improvements google made to the smoothness of the system in version 4.1 jellybean. it's part of the aosp code, so yes - this has project butter.

Added a Google Drive mirror. Can't upload to MediaFire though, cuz the file is over 200mb...

Well, this was obviously not updated in a while... I don't have much time to work on this nowadays, and anyways there's arco's work , so this is officially discontinued. Good luck to everyone with their projects, and have a good day! =======================================================...

yes, the value is ultimately set by the efuses, but it is a kernel module that is in charge of the value that is read from the /proc file, and that is hijackable with a rootkit. (you can see the module's source in the released me865 kernel source) about just flashing the file - is the mbmloader...

Seems that posting in the general forum about bootloader-unlock is really asking for pages and pages of "what exactly does that mean" and "good luck". (aka the thread posted in the link just below your post) not that it's bad, i'm just looking for some developers insight into what was actually...

did you consider trying to trick the updater into thinking the device is a ns one and flashing the ns mbmloader without trying to figure out the actual image layout? http://forum.xda-developers.com/showthread.php?t=1842394

Figured the original thread was too polluted so no one would even see if i post there.. so is anyone still working on this? i just got into this mess, and from what i saw most of what was tried here was listening on the motorola servers with cheesecake and praying for a lucky unlocked...

so did you try the hard reset? if you did, can you get into recovery mode (supposed to be A [QWERTY] + F [QWERTY] + Vol Down + Pwr) or s/w upgrade mode? (E [QWERTY] + Vol Up + Pwr) if you can get into either one you're probably ok. through recovery you can flash whatever, and through s/w upgrade...

how'd you try to flash the theme? through a custom recovery? and why did it stop? did you give hard factory reset a try? (dunno what exactly it resets but it might help, and it might actually be exactly what your phone is trying to do according to the screen output)...

the file staying an image file though you renamed it usually comes from windows hiding known file types' extensions. you can turn that off in your file browser through Tools -> Folder Options and somewhere over there there should be a checkbox that says "hide known extensions" or something...

assuming it does turn on, turn it on and plug it to your pc, then use adb (android debug bridge) which comes with the android sdk to pull files out of your phone. as for the contacts you can pull the sqlite db file...

BUMP Help?

Hey, Yesterday I got a sort-of-refurbished Nexus S (I9023) which was apparently not in such a good shape... Had problems flashing the system and userdata partitions (kept saying they were flashed fine but after reboot went back to their previous state). Stupidly, I followed some tip without...

-n is top's argument for iterations:

your updater-script didn't work because apart from changing its name, the scripting language it's coded in has changed from Amend to Edify. try looking for posts about converting scripts between the two.. I think there's an automated script for this somewhere or you can do it by hand.

try running: adb remount and then your root script. what it does is it remounts the system partition r/w instead of read-only, so you can chmod and such

etc is under the system partition on the android os

The vendor id in your udev file is the HTC vendor id.. you should use the samsung one: 04e8 Besides, you can just try: adb kill-server and then: sudo adb start-server and see if you can get your device listed

Android RTL Auto-Patcher You can use the Android RTL Auto-Patcher, its supposed to be pretty automatic, and it can even tell you if your rom is supported or not : http://forum.xda-developers.com/showthread.php?t=907635&highlight=%5BPC-UTIL%5D+Android+RTL+Auto-Patcher+%2B+ProTools+%28v.1.5%29

Being an "open source Home Replacement app", I spent a couple of hours yesterday trying to find a public repository where I could get ADWLauncher's code. Looking at its google projects page, it seems that the project is quite active, yet the latest source I could find is under the CyanogenMod...