Develop Bugs

[MOD] IncrediControl - Easy GUI Undervolting

Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229

Please confirm if this works or not. Tiamat 1.0.4 has:
ported sysfs interface for VDD levels from Tiamat_8x50 (cayniarb, eviollet)
But I'm not sure where the path to the levels are since I can't find the commit in his git.
EDIT: I found the commit, it looks like its SVS. I will update later and post a new build. I need an individual who is proficient with using adb or the terminal emulator to please pm me.

Chad, sorry, I know this is off topic, but does your Incredikernal work on the Incredible2?

rfarrah said:
Chad, sorry, I know this is off topic, but does your Incredikernal work on the Incredible2?
Click to expand...
Click to collapse
No it does not. I don't really like to do kernels for devices I don't have because its difficult to properly test. If someone comes across an extra device that they are willing to donate I'd be more than happy to start working on one though.

chad0989 said:
No it does not. I don't really like to do kernels for devices I don't have because its difficult to properly test. If someone comes across an extra device that they are willing to donate I'd be more than happy to start working on one though.
Click to expand...
Click to collapse
Okay, I didn't think so, but on the off chance they DID, I'd be downloading immediately. Your kernals - at least on my Incredible - were the Gold Standard. Thanks for all that work!
My DI1 died last Saturday and Assurion replaced with a DI2. Still getting my feet on the ground with it, but after rooting and loading MIUI, it's almost like a big DI1.
Anyway, thanks again.

Does anyone.know if the china version of sense3 work with this
Sent from my HTC Incredible 2 using XDA Premium App

Anybody available to test?

I would if I knew this china rom met the requirements
Sent from my HTC Incredible 2 using XDA Premium App

I wouldn't mind giving it a shot.
Sent from my Droid Incredible 2

ruvort said:
I wouldn't mind giving it a shot.
Sent from my Droid Incredible 2
Click to expand...
Click to collapse
Thanks, I'll be sending you a PM in a few minutes

I'll try it how do I know my kernel supports it
Sent from my HTC Incredible 2 using XDA Premium App

REDSCARFACE1 said:
I'll try it how do I know my kernel supports it
Sent from my HTC Incredible 2 using XDA Premium App
Click to expand...
Click to collapse
I believe Tiamat 1.0.4 is the only one that has user changeable voltage scaling right now. Are you running that one?
Edit: I think jdkernel stable 1.0.0.1 may also

Please make an incedikernel for our phones! I loved it for the Inc1

06stang said:
Please make an incedikernel for our phones! I loved it for the Inc1
Click to expand...
Click to collapse
Refer to http://forum.xda-developers.com/showpost.php?p=16075489&postcount=4
Maybe someone will fall over an exra refurb at some point or something. I'd love to just do it, but its really difficult on a short time schedule to wait for feedback from someone just to see whether or not something boots. Or if a new feature works. I usually go through 100+ testing builds between releases. Hope you guys understand.

i would too but i have no idea if my kernel supports it. i'm on jdkernel stable 1.0.0.1

bik2101 said:
i would too but i have no idea if my kernel supports it. i'm on jdkernel stable 1.0.0.1
Click to expand...
Click to collapse
I believe it might. I'm going to send you a PM.

Titmat does not work with china ota sense3 rom.
Sent from my HTC Incredible 2 using XDA Premium App

REDSCARFACE1 said:
Titmat does not work with china ota sense3 rom.
Sent from my HTC Incredible 2 using XDA Premium App
Click to expand...
Click to collapse
Then you will have to wait for a sense kernel that supports sysfs voltage changing. Sorry. I'm sure one will come around pretty quickly.

07/28/11 - Preview 5-2
Changes include:
A restore defaults button. NOTE: You must reboot for the changes to take effect.
A text box that lets you know if you currently have saved boot settings or not.
Support for SVS kernels (and subsequently support for msm7x30 devices, e.g. inc2)
Started to work toward database storage of voltages instead of boot scripts. There is still a boot script, but it has been relocated to /etc and is now run by a service at startup.
NOTE: As of now, the only inc2 kernel that supports voltage adjustment is Tiamat 1.0.4
Get it at http://www.incredikernel.com

chad0989 said:
Refer to http://forum.xda-developers.com/showpost.php?p=16075489&postcount=4
Maybe someone will fall over an exra refurb at some point or something. I'd love to just do it, but its really difficult on a short time schedule to wait for feedback from someone just to see whether or not something boots. Or if a new feature works. I usually go through 100+ testing builds between releases. Hope you guys understand.
Click to expand...
Click to collapse
Hope it works out. Love your work on the Inc1

CM9 or Cakulin's

Well, we all know how terrible the ICS update from Samsung was. I am in a situation where I need to go back to GB. I am thinking about Calkulin's rom, because it is based off on EL29 GB, which was very stable and had none of the issues Samsung introduced witht he ICS OTA update.
I know that CM9 is almost released to beta, and that there is an install guide for our phone using the Alpha 6 build. Since this is based on ICS, will all of the bugs in the Samsung released version be an issue here? I know the CM team is fantastic, but maybe I just don't understand how they go about creating a build for our phones.

I ran Calk 3.0 for months. Great ROM, virtually no problems to speak of. I just switched to CM9 and it's a little buggy, but I'm really enjoying it. If you want the safe route, go with Calk 3.0; If you're willing to deal with random issues, CM9 is your ROM.

Cm9 is great but the battery life just isn't there yet (not sure, may be ics in general).
I've gone back to EG30 and couldn't be happier.
Sent from my SPH-D710 using xda premium

pbassjunk said:
Cm9 is great but the battery life just isn't there yet (not sure, may be ics in general).
I've gone back to EG30 and couldn't be happier.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
EG30 stock+CWM ? or any specific rom to look at? links pls

Calkins EL29 is what I just went back to today, I was on Cm9, there is a serious data loss that needs to be fixed. Other than that it was amazing. Smooth, beautiful, but the data dropping out was to much for me. I'll wait for a beta and hope it gets fixed.

http://forum.xda-developers.com/wiki/Samsung_Epic_4G_Touch/ROMs
EG30, and then used the auto-root.zip that's floating around here somewhere.
Hasn't bugged me to update, but I'll look into that if/when it happens.

I'm still rocking Calk's 2.8.1

Nismo` said:
Well, we all know how terrible the ICS update from Samsung was. I am in a situation where I need to go back to GB. I am thinking about Calkulin's rom, because it is based off on EL29 GB, which was very stable and had none of the issues Samsung introduced witht he ICS OTA update.
I know that CM9 is almost released to beta, and that there is an install guide for our phone using the Alpha 6 build. Since this is based on ICS, will all of the bugs in the Samsung released version be an issue here? I know the CM team is fantastic, but maybe I just don't understand how they go about creating a build for our phones.
Click to expand...
Click to collapse
There are so many things wrong with this post I'm not quite sure where to start....
1. Not to flame you, but "we all" don't know how terrible ff18 is, as ff18 is the base for two of our most bulletproof roms ( blu kuban and goodness) and many other fine roms as well
2. If you "need" to go back to gb its either simply a matter of either personal preferance or the inability to troubleshoot using information posted all over these boards... there is nothing majorly wrong with ff18, it has a few small bugs, but overall is very solid... we did not see many complaints when people were running the leak before the OTA
3. CM9 is great, its also an AOSP rom, so it has nothing to do with any rom from Samsung. That the point of it. Still not sure what "bugs"you're referring to as you don't go into specifics...
Sent from my SPH-D710 using xda app-developers app

cp320703 said:
There are so many things wrong with this post I'm not quite sure where to start....
1. Not to flame you, but "we all" don't know how terrible ff18 is, as ff18 is the base for two of our most bulletproof roms ( blu kuban and goodness) and many other fine roms as well
2. If you "need" to go back to gb its either simply a matter of either personal preferance or the inability to troubleshoot using information posted all over these boards... there is nothing majorly wrong with ff18, it has a few small bugs, but overall is very solid... we did not see many complaints when people were running the leak before the OTA
3. CM9 is great, its also an AOSP rom, so it has nothing to do with any rom from Samsung. That the point of it. Still not sure what "bugs"you're referring to as you don't go I to specifics...
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
You should have read closer. He was asking IF CM9 had the same bugs as the Samsung update.
Sent from my SPH-D710 using XDA

CM9 doesn't have the same bugs as the sammy release totally different builds.
Go CM9 if you want the latest and greatest real ROM ever IMHO.

Dalmus said:
You should have read closer. He was asking IF CM9 had the same bugs as the Samsung update.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Not really, as I'm still not sure what bugs he's referring to in the first place, and any bugs in cm9 would be listed in the op/ changelog / etc of the cm9 thread anyway... but as its AOSP common sense dictates that it has next to nothing in common with an official build
Sent from my SPH-D710 using xda app-developers app

cp320703 said:
There are so many things wrong with this post I'm not quite sure where to start....
1. Not to flame you, but "we all" don't know how terrible ff18 is, as ff18 is the base for two of our most bulletproof roms ( blu kuban and goodness) and many other fine roms as well
2. If you "need" to go back to gb its either simply a matter of either personal preferance or the inability to troubleshoot using information posted all over these boards... there is nothing majorly wrong with ff18, it has a few small bugs, but overall is very solid... we did not see many complaints when people were running the leak before the OTA
3. CM9 is great, its also an AOSP rom, so it has nothing to do with any rom from Samsung. That the point of it. Still not sure what "bugs"you're referring to as you don't go into specifics...
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I disagree. I've been using the goodness ROM & I experienced the dreadful Android OS battery drain bug.
Sent from my SPH-D710 using xda premium

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Chew DZ said:
I disagree. I've been using the goodness ROM & I experienced the dreadful Android OS battery drain bug.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
again I wouldn't call that a bug... android os is going to use the most power outside of the screen, so if you don't have a lot of screen time it'll be a pretty high percentage... secondly do you have better battery stats installed? If its really using a lot of power you're probably not hitting deep sleep at any point, you need to figure out what's wakelocking it. The last thread I saw with a guy complaining about android os power use, when finally convinced to post screen caps of his better battery stats had something like 1300 wake locks, all he had to do was change a few settings... These things are not "bugs" in the rom as many of you are putting it but simple settings that you have that need to be changed in order to make the most efficient use of the battery. You've provided no evidence for this bug other than an anecdotal statement and I 100% gaurentee you if actual battery stats were posted a simple and obvious solution could and would be found. These threads are bad as they do not seek to solve any problems but only say things are broken, when they are not- every battery complaint could be solved just using the search bar- this is an enthuaist website and not everything will work 100% with no effort whatsoever on your part. Like the intro video used to say xda is not a place to come to make your phone cool, its for learning... ics is very different than gb and if you don't like it, fine, but don't post that things are broken or buggy when they are not and all that's needed is a search for information all ready posted to fix the issue. I'll post a screen cap of my battery life on goodness to support my point, I'm on stock battery and not running any tweaks other than properly sleeping....
Sent from my SPH-D710 using xda app-developers app

cp320703 said:
again I wouldn't call that a bug... android os is going to use the most power outside of the screen, so if you don't have a lot of screen time it'll be a pretty high percentage... secondly do you have better battery stats installed? If its really using a lot of power you're probably not hitting deep sleep at any point, you need to figure out what's wakelocking it. The last thread I saw with a guy complaining about android os power use, when finally convinced to post screen caps of his better battery stats had something like 1300 wake locks, all he had to do was change a few settings... These things are not "bugs" in the rom as many of you are putting it but simple settings that you have that need to be changed in order to make the most efficient use of the battery. You've provided no evidence for this bug other than an anecdotal statement and I 100% gaurentee you if actual battery stats were posted a simple and obvious solution could and would be found. These threads are bad as they do not seek to solve any problems but only say things are broken, when they are not- every battery complaint could be solved just using the search bar- this is an enthuaist website and not everything will work 100% with no effort whatsoever on your part. Like the intro video used to say xda is not a place to come to make your phone cool, its for learning... ics is very different than gb and if you don't like it, fine, but don't post that things are broken or buggy when they are not and all that's needed is a search for information all ready posted to fix the issue. I'll post a screen cap of my battery life on goodness to support my point, I'm on stock battery and not running any tweaks other than properly sleeping....
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Well its obviously been an issue with a **** load of people & they havnt mentioned anything about adjusting settings to fix it. What "settings" are you talking about?
Sent from my SPH-D710 using xda premium

Chew DZ said:
Well its obviously been an issue with a **** load of people & they havnt mentioned anything about adjusting settings to fix it. What "settings" are you talking about?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I can't speak to your device since you've not provided any information about it... however if you do full wipes when flashing, not no data, calibrate your battery and allow a few days to settle that's a good start. After that use better battery stats to determine exactly what is causing wake locks and not letting your device hit deep sleep and fix it... set up syncs properly and turn off unnecessary ones, use the toggles to turn off wifi, Bluetooth, and 4g when not in use.... these things will all help, a lot, and if done would probably solve 85% of the battery complaints that have assailed this board after the ota.... if you still are having issues look into phakers placebo script, or kobridges tweaks, search for people who have had similar issues and the solutions they've found for them, should you find it necessary to post about it after doing all of the afformentioned provide as much, detailed, information as possible including screencaps of your better battery stats, what rom/kernel you are on and the steps you've taken so far... the information is out there and people are willing to help, but simply posting "battery sux everyone thinks so" will not result in anything getting fixed... it is not difficult, it simply requires some research and problem solving
Sent from my SPH-D710 using xda app-developers app

cp320703 said:
I can't speak to your device since you've not provided any information about it... however if you do full wipes when flashing, not no data, calibrate your battery and allow a few days to settle that's a good start. After that use better battery stats to determine exactly what is causing wake locks and not letting your device hit deep sleep and fix it... set up syncs properly and turn off unnecessary ones, use the toggles to turn off wifi, Bluetooth, and 4g when not in use.... these things will all help, a lot, and if done would probably solve 85% of the battery complaints that have assailed this board after the ota.... if you still are having issues look into phakers placebo script, or kobridges tweaks, search for people who have had similar issues and the solutions they've found for them, should you find it necessary to post about it after doing all of the afformentioned provide as much, detailed, information as possible including screencaps of your better battery stats, what rom/kernel you are on and the steps you've taken so far... the information is out there and people are willing to help, but simply posting "battery sux everyone thinks so" will not result in anything getting fixed... it is not difficult, it simply requires some research and problem solving
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
How would you explain spotty, laggy menu/app load performance, High WiFi reconnects and battery usage on a Stock, OTA Sprint/Samsung update that was factory reset? People on the forums can't really correct these. They worked great in GB.

bottom line is if you want a stable rom that runs smooth as butter Calkulins e l 29 is great!

I ran Calks Roms for the longest time. He has made some great Roms but I think he's move on from the E4TG. I enjoy running the newest and often a bit buggy Roms currently on Blu Kuban (amazing). Calks 3.0 is pretty rock solid if your looking for a mostly stock rom with root and tweaks.

[Q] Porting CM10 A100 to A101

Hi Everyone, can anybody tell me how to port CM10 A100 to Iconia A101, coz I always use A100 ROM but I lose my 3G capability?
Thanks Before

Well, I you'd need 3g drivers. Etc maybe drop the 3g apps in? I may not be possible. Might also need source changes.
Sent from a Soviet base in Indiana

I know this thread is older... But to answer your question: it must be built into the source before compile it - just to sum it up. But that's what I want to do.
I planned some projects for A100/101
- build an existing Rom (cm9) with 3g to serve a101 users (cm9 is most stable)
- recovery with dual boot (and run Ubuntu n near android)
- start 4.2 builds
This is lot of work and will take a lot of time, any help appreciated.
Gesendet von meinem A100 mit Tapatalk 2

Eh. 4.2 was booting just no WiFi and lots of little UI stuff.
Sent from my vangogh using xda app-developers app

das_webos_transformer said:
Eh. 4.2 was booting just no WiFi and lots of little UI stuff.
Sent from my vangogh using xda app-developers app
Click to expand...
Click to collapse
Well, nice to know. Could be a good starting point.
Gesendet von meinem XT910 mit Tapatalk 2

dtrail1 said:
I know this thread is older... But to answer your question: it must be built into the source before compile it - just to sum it up. But that's what I want to do.
I planned some projects for A100/101
- build an existing Rom (cm9) with 3g to serve a101 users (cm9 is most stable)
- recovery with dual boot (and run Ubuntu n near android)
- start 4.2 builds
This is lot of work and will take a lot of time, any help appreciated.
Click to expand...
Click to collapse
How are things progressing? I found the following old info:
pio_masaki said:
It can have 3g just fine, I've asked a few times for the 3g ril files from 101 users wanting me to build for them, they always vanish and I never hear back about it.
A100 just had its rotation for builds last night / this morning so it'll come up again sometime between wed-fri I think. Been looking at updating the black bean build and maybe adding AOKP as well, I'll use them for testbeds. I may go ahead and just do an extra day on the A100 and see about getting a potential 3g build up for you.
Side note, sosei will use gps if you use the newer cm10 boot.img.
Current rotation is:
Nexus 7 holds priority as I've been invited to Team Sorcery as their N7 dev.
Toshiba Thrive 4.2 development, 4.1.2 updates and kernel work (voodoo sound) comes second as they've been extremely generous to me.
Droid DNA aosp porting as the device was pretty much donated
Slight GNex work as needed, rare
A100 is bottom/last as I don't own one, luckily fixes from the thrive usually directly move over to the A100
Other devices I don't own.
I have a few things planned for the A100 for some nice updates and releases to jeep you guys in a variety of ROMs, like AOKP and some updates to the cm9 kernel I use.
Sent from my Nexus 7 - JBSourcery 4.5
Click to expand...
Click to collapse

Things are going slowly... Too much work in the office. But I set up a working tree some weeks ago for CM9 and a kernel. As soon as I have some more time I'll continue this. I was also busy with a kernel for the moto razr. Once I had a whole team, but now I'm alone... Will take time.
M.o.t.o.r.o.l.a.R.a.z.r - JBX-Kernel 0.5a - Tapatalk4

sorry for revived such an old thread,
i've managed to port cm10 to iconia a101, 3g and other is working properly.
but it still got a couple of bug,just wanna know if there someone here who could help me fix some bug left (let's say like gps) :fingers-crossed:

What is your base and port ROM that you used? ie what CM10 rom did you use or did you build from source? What kernel did you use?
Also you need to be more specific on the issues that you have, as well as logcats otherwise there is nothing any of us can do.

I port the rom for a500 from tegra owner forum and using gm kernel with it,
So far bug that i noticed just the gps and flash,
The gps won't start, in the gps log it mention something wrong with the hal configuration
And i noticed that the file in /dev/bus/usb/002 doesn't exist which were the configuration was set to look.
I'll explain more specific and take a logcat tomorrow,it's already 2 am here got to work in the morning,
Thanks btw for your reply
Edit: for the base i mainly using your rom,and take some other part from some different rom
here the logcat and gps log when i tried to used gps.
Sent from my Galaxy Nexus using xda app-developers app

Your logcat is also indicating that you don't have 3g connectivity. I'm pretty sure the GM kernel does not have 3G support so no matter what you do and try to get working on this build, you won't have 3g connectivity. The first step to getting it to work is to find a kernel that has 3g activated on it.

hardslog said:
Your logcat is also indicating that you don't have 3g connectivity. I'm pretty sure the GM kernel does not have 3G support so no matter what you do and try to get working on this build, you won't have 3g connectivity. The first step to getting it to work is to find a kernel that has 3g activated on it.
Click to expand...
Click to collapse
A stock a101 ICS kernel should function well enough for testing this in 4.1.
Sent from my Galaxy Nexus using Tapatalk 2

That's what I was thinking too. I just might try that as i have had success doing the same thing with a TF300 to get 3g working
Sent from my A100 using xda app-developers app

hardslog said:
That's what I was thinking too. I just might try that as i have had success doing the same thing with a TF300 to get 3g working
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I've been meaning to look at 3g for the thrive also, may as well start noe since others are looking at it too lol
Tapatalked from my HTC DNA - Carbon

hardslog said:
Your logcat is also indicating that you don't have 3g connectivity. I'm pretty sure the GM kernel does not have 3G support so no matter what you do and try to get working on this build, you won't have 3g connectivity. The first step to getting it to work is to find a kernel that has 3g activated on it.
Click to expand...
Click to collapse
3g was working just fine, i've tried with several kernel including stock ics,

I'm interested in helping out fauntelroy, was going to start porting a rom, but there seems little point in re-inventing the wheel.
No idea if you're still working on it though, let me know, thanks!

[WIP][ROM][DEV]Ubuntu Touch 5/7

Okay everybody, I want to start a WIP on this as it seems that we can get somewhere. The last dev seems to have dropped the project so I picked it up. :good:
***NOTE*** This is meant for development/testing purposes ONLY. It is in NO WAY for the faint of heart and you must follow ALL instructions or it will not boot! You have been warned!
As of 5/7/2013, the following things are working:
Camera (flash works, it takes pictures)
Sound (the only reason I know this works is because the shutter noise goes off in the camera app, there is no other way to test this right now)
The test apps (browser, notepad, gallery, camera, browser, phone, calculator, calendar, clock)
Power button (phone goes to sleep and wakes, hold the power button down to shut off the phone - the shutdown takes a second because it shuts down just like a linux kernel would - plug it in the charger to test this, it will vibrate once it is off)
Not working - just about everything else. Most items are still placeholders and there is a stability issue where the apps all close themselves after a few seconds which I am trying to figure out. There is no data or cellular connectivity of any kind. This may be fixable, however, since I was able to get the camera working by pulling the prebuilts from a different CM version. I'll keep experimenting with this. If you put the device to sleep, it does not wake up to the same brightness (it is dimmed) and you can not adjust the brightness right now (working on this as well, its a permissions issue in the kernel source but I haven't been able to narrow it down yet).
It is VERY finicky about how it is installed. I won't give any support for anything but TWRP 2.5.0.0
To install:
-Download the kernel zip and the latest daily from Ubuntu (I will post links later)
-Backup your current ROM in its entirety using TWRP - check every item on the list or you may have to go to a fresh install of your version you were running previously.
-In TWRP (once again, make sure its 2.5.0.0 because these are 2.5.0.0 specific instructions), factory reset but do an advanced reset, check dalvik, data, system, and cache. ***MAKE SURE THAT YOU DON'T FORMAT YOUR MICROSD***
-Install the kernel zip and do not wipe cache or dalvik
-Install the Ubuntu preinstalled image, once again make sure you do not wipe the cache or the dalvik.
-Do not do anything else, no fixing permissions or anything, just reboot
-Wait about 2 minutes for the lock screen to come up and then you can use it
I will keep working on the kernel - the other functions will not work until Ubuntu implements them.
This is my first time working with actual development - if anyone wants to give me a tutorial to get my project up on GitHub so everyone can work on it, I would be more than happy to do so.
Here are the links:
Kernel built 5/7/2013: http://d-h.st/185
Latest Ubuntu Touch base: http://cdimage.ubuntu.com/ubuntu-to...current/raring-preinstalled-phablet-armhf.zip
Since the source has been moved to Raring Ringtail, there should not be a need to update that link. Please note that the 5/7/2013 build is the one that I tested and be sure to let me know if it gets broken in the future.
Enjoy everyone and once again, if you want to contribute, I'm more than happy to set up a GitHub, I just need some basic help getting it started.

Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium

TheLastSidekick said:
Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I am hoping that development will take off. Ubuntu is set to start releasing alpha apps on the 16th so figuring out how to get a working kernel for it was top priority for me and nobody else seemed interested in doing it.
I've literally spent hours, lots of expletives, and other unpleasant things trying to get this built. I think I should have started working with CM BEFORE taking on UT but it paid off

Thank you sir,

Dling now
Sent from my Galaxy Nexus using xda premium

Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium

ktetreault14 said:
Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.

EtherealRemnant said:
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.
Click to expand...
Click to collapse
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium

eggydrums said:
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The kernel is a CM base. Its a massive fork of CM that's kind of a royal pain in the ass to work with since its not been synced since they forked it and they've made major modifications to the code (all traces of Dalvik are gone, for example). You also have to make modifications to the kernel build so it functions more like a linux system, there are process patches that have to be applied to the kernel, etc.

Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.

Cannot wair for Ubuntu to be fully released, I would like to use this as a daily driver
Sent from my SGH-T999 using xda premium

charlieb620 said:
Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.
Click to expand...
Click to collapse
So you had the same issue with your build?
Admittedly, I never tried it because I was determined to build my own and yours was March dated. I had posted in the thread trying to get some assistance from you actually - but yeah, its certainly not usable right now.
Was your kernel a forced M1 or did you somehow find a way to get the nightly source to build? I've built M1 and M2 so far. Since I had the same results with both and UT is based off of M1, I haven't messed with M3.
I wish I could figure out the WiFi and the force close of apps - did you patch the kernel successfully? I added the proc patch as best I could (raw data paste but it didn't throw warnings so it must have worked - I'm not a programmer) and it didn't fix anything, apps still just close after a few seconds.
I was surprised that I got the camera and sound though just by switching CM versions. Maybe the same thing can happen with the WiFi? I noticed that it is being built as a module but I don't know enough about the Android kernel to reconfigure it as a built-in (I don't know if the Ubuntu kernel has the code for detecting all the hardware just yet, I'm guessing it doesn't). I've done lots of Linux kernel tweaking (I have toyed with it since Red Hat 1.0 and its my daily driver in the form of Ubuntu 13.04 right now - usually I use Mint but I wanted to eliminate as many variables as possible) but I don't know much about Android.
Admittedly, I started with UT before I had ever worked with CM even so I've learned a LOT. lol

Thanks for this.

So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app

biohazard said:
So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It should work fine with the latest DP. I haven't bothered to update it because the kernel source hasn't really been worked on. They're still focusing all of their work on Google devices.
There isn't a stable kernel for any S3 variant right now.
Sent from my SGH-T999 using Tapatalk 4 Beta

Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium

biohazard said:
Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Make sure you followed the directions exactly, any deviation will cause it not to boot. Also there is no boot screen. What you can do is plug it in to the charger before you boot it - if it fails to boot the phone will power off and take you to the charging screen. If it doesn't, give it a few minutes to load up especially the first boot.
If it fails again, let me know and I'll see about building a new kernel some time this week. As far as I am aware there is no newer kernel source on the Ubuntu side but I can try to build an RC5 based kernel (this is an M1 kernel).
Its worked for everyone else but I can't test it right now because I'm getting ready to go out and need my phone.
Sent from my SGH-T999 using Tapatalk 4 Beta

Alright I see, thanks for all the help. Could you possibly point me to the correct base download, I have tried multiple phablet bases, and I just can't get it to boot for some reason. Thanks in advance for all the help.
Sent from my SGH-T999 using Tapatalk 4 Beta

The international GS3 has working wi-fi.....i know the hardware is completely different but do you think you might be able to look at how they got it working over there?
http://forum.xda-developers.com/showthread.php?t=2315397
Here's the commit that shows how he got wi-fi working: https://github.com/Androguide/andro...mmit/feac1d9af58c2947e0f3f6b6719553be5811ce6d try applying that to init.qcom.rc i would but my computer won't build anything i'm trying to fix it...
Also for github you really just need to post your manifests file and whatever you've modified from the source code. i'm not really a pro with github but i've worked with it quite a lot. They have an awesome tutorial on their website i'd recommend checking out.

Okay Ubuntu made upstream code changes that broke the kernel. Give me a few days and I'll have an update.
Plays2 - that patch *should* work for us as well since we use Broadcom's WiFi just like the international version does (odd that they didn't use Qualcomm's since it came with the SoC but it works in our favor in this instance). Still takes a lot of configuration to get it running though.

[ROM][21-12-2013][CM 10.2] 4.3.1 - Jelly Mod - v1.0

Hello XDA and welcome to your Christmas present from me! Jelly Mod is basically Nevergone's 4.3 build from CM source with various added tweaks from myself. Before I start, I would just like to give major props to: Cyanogen Mod, Google, HTC, Flinny, Flemmard, guest1, mosi110, kylon, szezso, nadlabak and NeverGone\RU. Without them our device would suck, literally. Also before anyone asks, KitKat is in the pipeline! Please post any comments, bad links or improvements. This will help make the ROM better. Thanks for downloading, don't forget to hit thanks!:good:
Bugs:
GEL "Ok Google" not working;
Data usage calculation bug; (probably never going to be fixed:crying
You tell me!
Features:
Based on CM 10.1;
Android 4.3.1;
Blazing fast!!
Latest Gapps;
Various battery percentage in status bar options;
Choice between GEL and Trebuchet;
Newer Trebuchet, with live folders, icon pack support and other stuff;
Supported on the G2 and Desire Z;
Hosts tweaks, no ads!
Build prop tweaks;
Advanced reboot;
T9 dialer;
Camera button options (wake/unlock/peek/playback control);
All device hardware fully functional, including wifi, bluetooth, camera, camcorder, etc;
Bloatware and unnecessary applications removed;
Rooted, deodexed and slim!
All apks zipaligned on boot (makes apps load faster);
Faster internet and battery tweaks;
Better jpg image quality;
Better camera recording quality;
Smoother video streaming;
Faster wifi connect/disconnect;
Overall smoothness improvements;
See for yourself! Browse through settings and find something to your liking!
Version 1.0.0:
CM source.
Install:
Coming from another ROM?
-Wipe data, wipe cache, wipe dalvik cache, install ROM, install Gapps and let it settle for a few minutes.
Just an update?
-Wipe cache and dalvik cache, install new version of ROM. Any problems? Follow "Coming from another ROM?" steps.
Download:
https://sites.google.com/site/masterleron/
Sources:
Thanks to NeverGone\RU:
Local manifests: https://github.com/NeverGone-RU/Andromadus
Device tree: https://github.com/Andromadus/android_device_htc_vision
MSM7x30 common: https://github.com/Andromadus/androi...msm7x30-common
Kernel: https://github.com/Andromadus/htc7x3...andromadus_4.3

Reserved...
Sent from my Nexus 7 using Tapatalk 4

Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Gonna try soon!! Thanks a lot!
Sent from my HTC Desire Z using xda app-developers app

http://forum.xda-developers.com/showthread.php?t=2544330
Also what does this have over NeverGone's 4.3 which has been running great for me for weeks on end?

HTCDreamOn said:
http://forum.xda-developers.com/showthread.php?t=2544330
Also what does this have over NeverGone's 4.3 which has been running great for me for weeks on end?
Click to expand...
Click to collapse
Remember Jelly Baby, it has all of those tweaks plus some more as its 4.3.1 I would try both, but this is definitely blazing! BTW it's not just build prop tweaks, I spent a LOT of time on this. I wouldn't release a new ROM just for build prop tweaks, and judging by that thread, most of which are just placebo anyway.
Sent from my HTC Vision using Tapatalk

wow, nice job. I'll try it for sure.

HTCDreamOn said:
http://forum.xda-developers.com/showthread.php?t=2544330
Also what does this have over NeverGone's 4.3 which has been running great for me for weeks on end?
Click to expand...
Click to collapse
*cough*...
I'm not saying it's that terrible, though. Maybe someone will want to use my build shipped with GEL and with mobile data fixed out of box.

NeverGone\RU said:
*cough*...
I'm not saying it's that terrible, though. Maybe someone will want to use my build shipped with GEL and with mobile data fixed out of box.
Click to expand...
Click to collapse
Mine has GEL and mobile data out of the box as well. Those tweaks are proven to work BTW. Oh and mine is faster.
Sent from my Nexus 7 using Tapatalk 4

Thanks to everyone who appreciates my work.

masterleron said:
Mine has GEL and mobile data out of the box as well. Those tweaks are proven to work BTW. Oh and mine is faster.
Click to expand...
Click to collapse
That's exactly what I'm saying -- GEL and mobile data are the only differences in your build.
"Faster" with only media "tweaks" applied to build.prop? Mind sharing how is it possible?
Speaking of "proven to work"...
LaraCraft304 in [URL=http://forum.xda-developers.com/showthread.php?t=2544330]demystifying build.prop[/URL] thread said:
Entries that DO NOT exist in the source:
(Again: I scaveged all Android source code)
...
ro.media.dec.jpeg.memcap
...
All ro.media.enc* entries
A more elegant alternative would be to edit /system/etc/media_profiles.xml
Click to expand...
Click to collapse
These are the only tweaks you applied. It just can't be "faster" in any way possible.
Initially I thought that you finally managed to build Android from source - after all PMs you sent me, you should get at least somewhere!
Honestly, I was disappointed.
Again, it's not bad that you're modifying others' work -- we all started with something small. But then you should at least give a proper description of your work and not claim something that isn't true. Remember, running a diff between two builds will show everything you did, and trying to cheat here won't do anything good.
At the moment, JM is my build with GEL on top of it.
I believe you'll add more features to it. Ad-blocking hosts file, zipalign scripts, maybe some apks removal -- all that is currently missing.
Just be fair, that's the only thing I'm asking you as a developer.

NeverGone\RU said:
That's exactly what I'm saying -- GEL and mobile data are the only differences in your build.
"Faster" with only media "tweaks" applied to build.prop? Mind sharing how is it possible?
Speaking of "proven to work"...
These are the only tweaks you applied. It just can't be "faster" in any way possible.
Initially I thought that you finally managed to build Android from source - after all PMs you sent me, you should get at least somewhere!
Honestly, I was dissappointed.
Again, it's not bad that you're modifying others' work -- we all started with something small. But then you should at least give a proper description of your work and not claim something that isn't true. Remember, running a diff between two builds will show everything you did, and trying to cheat here won't do anything good.
At the moment, JM is my build with GEL on top of it.
I believe you'll add more features to it. Ad-blocking hosts file, zipalign scripts, maybe some apks removal -- all that is currently missing.
Just be fair, that's the only thing I'm asking you as a developer.
Click to expand...
Click to collapse
I haven't claimed anything, how am I cheating, its not hard to add hosts scripts and stuff, I'm still working, this is only the first build. If you don't like it, then why tell me I can build from source and give me tips. Jelly Baby started small like this and look where it is now. I WILL add more tweaks, calm down. Now can we please keep this on topic. Also, I've read various places that those build prop tweaks work, one post in some random thread is not going to change my mind.
Sent from my Nexus 7 using Tapatalk 4

masterleron said:
I haven't claimed anything, how am I cheating, its not hard to add hosts scripts and stuff, I'm still working, this is only the first build. If you don't like it, then why tell me I can build from source and give me tips. Jelly Baby started small like this and look where it is now. I WILL add more tweaks, calm down. Now can we please keep this on topic. Also, I've read various places that those build prop tweaks work, one post in some random thread is not going to change my mind.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
If you refuse to build from source you're gonna have to do more things than zipkang and chuck in some build.prop tweaks. Also listing features that are already in CyanogenMod such as T9 dialer isn't gonna fool anyone. Of course you've read in various places that those tweaks work, the amount of stupid scripts in the software development and hacking section of XDA is absolutely astounding. However there are multiple people who have been through the actual source code of android and PROVED that the build.prop tweaks do not work (http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/ ; http://forum.xda-developers.com/showthread.php?t=2544330). Note how I say proved: these people haven't made grand claims and fancy signatures, they've observed, tested, and given an objective answer.

Ok you guys stick with your opinions. As long as others are happy I don't mind.
Sent from my HTC Vision using Tapatalk

Q: I grep-ped through the source code and in no place those props are used. Are you milking thanks?
A: STFU Science, as long as people believe it's faster.
Oh, I'm gonna love this.

Based on CM10.2 (like in title) or on CM10.1 (like in op) ?
Sent from my Nexus 5 using Tapatalk

If you have a problem stfu and leave, its based on cm 10.2
Sent from my Nexus 7 using Tapatalk 4

masterleron said:
If you have a problem stfu and leave, its based on cm 10.2
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
don't worry, maybe you misunderstood me, I only asked because I've seen two different texts between the title and op.
I am mod of another forum and would like to publicize your new rom (and install and test it on my desire z) .. I just wanted to be sure that i've read it right .. no problem

Oh thx, sorry it's just a bit frustrating random people coming on my thread and basically having a go at me. But thanks.
Sent from my Nexus 7 using Tapatalk 4

masterleron said:
Oh thx, sorry it's just a bit frustrating random people coming on my thread and basically having a go at me. But thanks.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Random people? Someone like NeverGone\RU who has been here a lot longer than you deserves a lot more respect.
I told you stating you were 13 was stupid. I tried "your" ROM and it worked pretty well. Hell I actually used it as stable for a couple of months. Now I was going to try this ROM out but first, you have been blantely showed off as a rip/copy. I dont care but that in the XDA community is a NO NO. Later a complete disrespect for someone like NeverGone who has obviously had more time deving that you.
And Im not a fan of things NeverGone has done either, Ive ripped on him too so this isnt me being his fan or a antimasterleron.
I apoligize to myself for actually thinking you were a real dev. Shame, you had potential but you ruined it.