Database Develop

mssmison's Eclair V8 April 7th

I've done everything I can to audio. I'm sorry guys but I can't figure out bluetooth audio. Someone start a bounty and we'll see if we can get DZO to fix it I'm going to be slowing down on releases for a while, I'll still help people out, but don't expect much new from me for a while. If you're working on a build and have a question pm me and I'll help you out
V8
We're going QVGA only on this one.
Now based on my own source tree build.
Updated messaging app, check settings within app to change settings, now full screen.
Full screen AOSP apps.
Updated Helix Launcher, (app drawer is 5x5 and transparent)
New 'Car Home' Launcher from the droid 2.1 update. Nicer square launcher. much more car friendly I think.
Optimize on first boot. It will take a little longer..
Spare Parts now in Settings
No more swap or compache
Instructions;
I recommend you wipe, it may work if you don't but you may have issues
Boot, when launcher first opens, do menu ->confirgure to set to full screen.
The notifications pull down is accessible by doing menu->notifications while on the launcher.
Known Issues
Possible landscape issues with Launcher
No BT audio
No camera
V7 Changes;
- Optimize on first boot. It will take a little longer..
- Random Boot animation, Create a folder on your sdcard called bootanimation and put them in there (get some from here; http://forum.xda-developers.com/showthread.php?t=624480)- you MUST remove the spaces in the names.
- minor cleanups to fs.
- removed corpcal, (it really slows things down) install via update file
- Removed Bruts maps, latest maps is way better,
- Fixed VogueParts issue for converting to hvga
- Proper Vending.apk for all res (thanks to polyrhythmic)
- Removed AlarmClock.apk (donut) and replaced with Vogueified (new word) DeskClock
- updated news and weather widget to work with deskclock
- Adjusted prop for market.
- Added Nav Launcher
- Added Dialer One. More like htc dialer, auto contacts lookup etc.
- Some more speed tweaks
PREVIOUS CHANGES;
V .6a
Changes.
Nothing changed with the system, only the config app.
Vogue Parts app changes;
- Removed the swappiness option for compache, (it wasn;t working properly) I set swappiness to be static at 60
-Changed the way optional apps are installed (now installed to /data/app for update purposes)
What's not working?
Bluetooth audio, (regular bluetooth connections work fine, just not audio)
Camera, (it's on the list I promise)
Recommended paritions on sd card
2 ext2 paritions, 1 linux swap parition
Download
http://www.mediafire.com/?z0ejnm13woq
Kaiser Wifi Update,please use these files
http://forum.xda-developers.com/showpost.php?p=5914507&postcount=224
NBH Downloads
Currently DZO has posted an updated 320x240 nbh on his site. I've asked him to put the rest of the resolutions on as well.
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Thanks to Jesse and Martin!

Nevermind. Downloading

mssmison,
Glad you are back with your builds!
Questions...
Q-1: You mentioned "Flash".Does this mean this won't run on an SD card?
Q-2: You mentioned this is a "320x480 only right now".
So, this won't work on my Vogue?
Thank you!

JM-PDA said:
mssmison,
Glad you are back with your builds!
Questions...
Q-1: You mentioned "Flash".Does this mean this won't run on an SD card?
Q-2: You mentioned this is a "320x480 only right now".
So, this won't work on my Vogue?
Thank you!
Click to expand...
Click to collapse
You can use 320x480 on the Vogue. Hero builds use 320x480 and they look great

JM-PDA said:
mssmison,
Glad you are back with your builds!
Questions...
Q-1: You mentioned "Flash".Does this mean this won't run on an SD card?
Q-2: You mentioned this is a "320x480 only right now".
So, this won't work on my Vogue?
Thank you!
Click to expand...
Click to collapse
Not sure about haret. 320 x 480 just means you need to flash the 320 x 480 nbh for it to work.
mssmison - Do you got any screenies? Did you get the nexus launcher in this build?

I'm getting launcher force closes and restarts but not to the boot screen just the splash screen. I've never experienced this on any build. I did a fresh install and flashed the nbh that was included. It was real laggy but after a couple restarts and waits on launcher force closes it did speed up a bit.

hmmm, try another fresh erase and install, after setup wizard let it sit till it's fully loaded before you do anything.

Great work!
Sorry if Kaiser folk annoy you but was wondering if anything was done to the .nbh (changing the size of system/data partitions, etc.) to make this work on the vogue? I'd like to try it on my kaiser but was wondering if I need to tweak anything before i flash.
Don't worry, I don't plan to change a couple things and release it as my own
If there is something to change in the nbh I might upload a couple for Kaiser users with your permission.

Great work!
Sorry if Kaiser folk annoy you but was wondering if anything was done to the .nbh (changing the size of system/data partitions, etc.) to make this work on the vogue? I'd like to try it on my kaiser but was wondering if I need to tweak anything before i flash.
Don't worry, I don't plan to change a couple things and release it as my own
If there is something to change in the nbh I might upload a couple for Kaiser users with your permission
Click to expand...
Click to collapse
I think you just need to select the eclair3ddrivers in system type, when creating the zImage

Screens:
{
"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"
}

thanks for posting the screens

Drewden - How's this work for you? how's the speed for you compare to the original eclair build? I couldn't get this build working quite right but I'm going to attempt it again later today. The first norootfs build worked pretty good for me and was pretty fast for an eclair build.

I tried to add my own apps into the system image but I am getting an issue with the installation of the .tar file. Its telling me I don't have enough space... Should I make a bigger partition on my sd card for the system image?

Reddog80p said:
Drewden - How's this work for you? how's the speed for you compare to the original eclair build? I couldn't get this build working quite right but I'm going to attempt it again later today. The first norootfs build worked pretty good for me and was pretty fast for an eclair build.
Click to expand...
Click to collapse
I'm in the same boat. version 1 + the update worked awesome. it was fast and never really gave any problems beside the hw3d stuff not working properly.
This build is pretty slow, and the launcher is constantly force closing or hanging the phone when trying to open the launcher.
I did get the launcher to open once, and it looked sweet. if this build could get tweaked to run as fast as the first build and be more stable it would great.
Lots of potential here, but for now i'm going back to 1.0 as the os is more stable.

My bad wrong thread

I got this one running pretty alright, I am using Home++ app so no FC issue for me. It's faster and much stable compared to 1.0, Dialer/Phone app is tad bit faster. Compcache/Swap setting is cool.
But I am use to 240 build, so I am not getting any love. I am looking forward for QVGA build that Craig talked about...
EDIT: It gets even more responsive when Compcache is reduced to 16 (did after drewden said). Even dialer comes in less than a second. Now just want 240 version...

Reddog80p said:
Drewden - How's this work for you? how's the speed for you compare to the original eclair build? I couldn't get this build working quite right but I'm going to attempt it again later today. The first norootfs build worked pretty good for me and was pretty fast for an eclair build.
Click to expand...
Click to collapse
It's running pretty well for eclair. it has its moments but I set the homescreen to stay in memory and enabled compcache @ 16 meg. The launcher fc's stopped after that. I'm not too sure on the compcache/swap thing so if somebody could fill me in that'd be great, as id like to know the optimal setting.

Reddog80p said:
Drewden - How's this work for you? how's the speed for you compare to the original eclair build? I couldn't get this build working quite right but I'm going to attempt it again later today. The first norootfs build worked pretty good for me and was pretty fast for an eclair build.
Click to expand...
Click to collapse
you could also try setting max app processes to 4 in development settings

Hey Incubus, can you put up a list of all widgets you use on your screenshoot?

JeckyllHavok said:
Hey Incubus, can you put up a list of all widgets you use on your screenshoot?
Click to expand...
Click to collapse
sure,
beautiful widgets 2.36
eRay widget 2.15
Pure Messenger Widget 1.2.8
Dual Mount sd widget 1.6
Taskiller
Facebook
LastFm
News and weather widget
Xbox Live Avatar Widget
Tech Buzz
Calendar
Power Control

[MOD] LCD Density - DIY!

Ok guys, people seem to be having problems using the LCD Density changer app, so I am making this write up to help you out
If you would like to make your Droid X look like this...
{
"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"
}
Then follow these steps.
Method 1 - ADB
1. Download LCD Density w/ 2.2 market Fix - This also contains the 2.2 market fix (without the stagefright)
2. Put the build.prop in your android-sdk\tools folder
3. Connect your phone via usb, make sure it shows up with adb devices
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
Method 2 - Root Explorer
1. Copy the build.prop to the root of your SD card
2. Long press on build.prop
3. Select "Copy"
4. Navigate to /system
5. Click R/W in the top right corner
6. Paste, and overwrite
7. Reboot
Your screen will now look like this, giving you much more space. And If using ADW launcher, you can use 6 X 5 rows of icons!!
Now if you really like to do things yourself, in the build.prop..
Change
ro.sf.lcd_density=240
to
ro.sf.lcd_density=200
push, reboot.
If you want to revert back, just push this Stock Build prop back into place.
Credit to the guy who made LCD Density app, but it did not work with Droid X phone and koush's recovery installed. People had to SBF, so this post was necessary.

does this change the resolution ? does it affect any apps from running correctly ?
Looks great, I think I'd like to try it. Just want to make sure it's safe I guess.

JustinD2473 said:
does this change the resolution ? does it affect any apps from running correctly ?
Looks great, I think I'd like to try it. Just want to make sure it's safe I guess.
Click to expand...
Click to collapse
Its safe, I've tested and ran this in other forums.
You can read others trials here...
http://androidforums.com/droid-x-all-things-root/163974-mod-lcd-density-diy.html

Jacked mine up.. the method works fine, the only problem is that apps are completely screwy now.. the apps only show up in the original size so if your screen is 4 inches the app is only displaying in like 2.5 inches of space and the rest is just black now, also cause some fuzziness with some various icons in the notification bar ( battery etc).. definately gonna revert back

Joe92T said:
Jacked mine up.. the method works fine, the only problem is that apps are completely screwy now.. the apps only show up in the original size so if your screen is 4 inches the app is only displaying in like 2.5 inches of space and the rest is just black now, also cause some fuzziness with some various icons in the notification bar ( battery etc).. definately gonna revert back
Click to expand...
Click to collapse
Weird. Works perfect for me.

LexusBrian400 said:
Weird. Works perfect for me.
Click to expand...
Click to collapse
Only seemed to have resolution problems in the root explorer app, all other apps work fine Aside from that, i think 200 is probobly a little on the low side, may try 220 or 230 for a improvement

Yea I love it but a few of my apps are also little now. I'm gonna rock it tonight and see how I feel in the morning.
Sent from my DROIDX using XDA App

Worked well for me as well.
Thanks very much.
FYI
I couldnt adb remount (got an error, not sure why but whatever)
I had to boot into recovery, then do an
Code:
adb shell
then just (assuming your modified build.prop is on the sdcard root)
Code:
mv /sdcard/build.prop /system
exit & reboot!

230 was a good middle ground

Yeah, I like how it looks mostly but some apps don't strech which is kinda annoying. I'll give it a shot for a day or two and see what I think.
Sent from my DROIDX using XDA App

JustinD2473 said:
Yeah, I like how it looks mostly but some apps don't strech which is kinda annoying. I'll give it a shot for a day or two and see what I think.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Let me know what you think about it.... would Launcher Pro dock items still be the same size???

i recently Download app running 2.2. Changes resolution to 220 and let app reboot phone only to be stuck on Black screen after moto logo.tried rebooting and wiping with no luck. PC wont connect with phone either... i can only get into system recovery> any ideas guys????

jdifiore1 said:
i recently Download app running 2.2. Changes resolution to 220 and let app reboot phone only to be stuck on Black screen after moto logo.tried rebooting and wiping with no luck. PC wont connect with phone either... i can only get into system recovery> any ideas guys????
Click to expand...
Click to collapse
Yeah, dont use that app. That is the whole reason I created this mod. That app is causing problems.
Restore your nandroid backup, assuming u were smart enough to make one before messing with the phone the like that IF not, now you know! always nandroid before a mod!!!

i wasnt smart enough.. i guess that means my phones shot???

jdifiore1 said:
i wasnt smart enough.. i guess that means my phones shot???
Click to expand...
Click to collapse
No. I'll help you out. Do you use Gtalk? if so, PM me your email so we can make this easier.

CPUBoostLite --Now in Market (support and discussion still available here)

This app is now available for download in the google android market. Feel free to still post questions/comments/suggestions in this thread
V1.6
released in market. Search cpuboostlite for free version. Cpuboostpro ad-free version available.
V1.5
Fixed force close if phone is rebooted before app has been opened for first time or if app is pre-installed in a rom
Fixed issue where screen off/on settings would get mixed up if you opened app immediately after waking phone
CPUBoostLite1.5
V1.4
super user pop up notifications fixed(still popup at the times when it's supposed to but not all the time like some people were having.
slightly transparent widgets same theme...thanks workshed
CPUBoostLite1.4
V1.3
Added a second style of widget(choose from advanced settings which theme you want)
CPUBoostLite1.3
V1.2
Cleaned up widget a little. See new pic below.
Rewrote some code so only one service running in background
CPUBoostLite1.2
V1.1
Fixed Widget going blank when rotating phone
Added an About section with link to this page.
CPUBoostLite1.1
V1.0
Overclocking app
widget to show settings
screen on/off profile
set at boot option
Obviously there are other options already availble for this but I thought I would start with something simple for a first app. I appreciate any testing and feedback. This app does have some adds in it. If anybody has other rooted android phones to test this on that would be alot of help too.
The widget also displays the battery temp once you open the app or reboot the phone. I am still working on that little bug.
{
"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"
}

i downloaded the one you have in the op of celb yesterday or the day before.. is this different?

Not bad. I like it.
Sent from my nonsensikal froyo using XDA App

frosteddroid said:
i downloaded the one you have in the op of celb yesterday or the day before.. is this different?
Click to expand...
Click to collapse
yes i posted in the thread...this adds a few more options.

Conap said:
yes i posted in the thread...this adds a few more options.
Click to expand...
Click to collapse
awesome thanks conap.

This is fantastic Conap. Will this allow me to set the Screen Off Max on the Smart Ass Governor? That's been a sticking point for me that's kept me on CELB 3.5, which for me was a lot faster. When I listen to audiobooks with audible and the screen is off, v 3.6 and later would become somewhat unresponsive when I press my headset button to start and stop playback. Sometimes as long as 30 second delays.

icbeer said:
This is fantastic Conap. Will this allow me to set the Screen Off Max on the Smart Ass Governor? That's been a sticking point for me that's kept me on CELB 3.5, which for me was a lot faster. When I listen to audiobooks with audible and the screen is off, v 3.6 and later would become somewhat unresponsive when I press my headset button to start and stop playback. Sometimes as long as 30 second delays.
Click to expand...
Click to collapse
Yes you can choose your governor and then set the screen off settings. I hope it fixes your issue. You can also use a different governor if the smartass governor doesn't work for your needs.

Congrats on your first official app! I'm downloading this version until your ROM version is the same.

Conap said:
Yes you can choose your governor and then set the screen off settings. I hope it fixes your issue. You can also use a different governor if the smartass governor doesn't work for your needs.
Click to expand...
Click to collapse
Will this app help me with flash on my rom? ill try it on my x bro and let u know

Seems to work good for me! I definitely like having the option to change the governor.

Awesome. I maintain 7 Eris phones for family members.... this helps loads =)

I'm glad they finally put a thanks button on here so I can let Conap know how much I appreciate all the work

@Conap. I hope you don't mind a suggestion to add version numbers to this app (and also to post the version # in the thread title).

roirraW "edor" ehT said:
@Conap. I hope you don't mind a suggestion to add version numbers to this app (and also to post the version # in the thread title).
Click to expand...
Click to collapse
That's definitely a win idea. Though I'm really happy with it as is. I don't know if I'm ever gonna bother updating unless I discover some kind of bug.
This is the kind of bare-bones OC I've been looking for.

roirraW "edor" ehT said:
@Conap. I hope you don't mind a suggestion to add version numbers to this app (and also to post the version # in the thread title).
Click to expand...
Click to collapse
Yeah You are right...consider this v1 and we'll go from there lol.
5thAgent said:
That's definitely a win idea. Though I'm really happy with it as is. I don't know if I'm ever gonna bother updating unless I discover some kind of bug.
This is the kind of bare-bones OC I've been looking for.
Click to expand...
Click to collapse
Yeah I really was going for simple. I don't need anything fancy to set my cpu speed. Glad you like it.

Conap said:
Yeah You are right...consider this v1 and we'll go from there lol.
Yeah I really was going for simple. I don't need anything fancy to set my cpu speed. Glad you like it.
Click to expand...
Click to collapse
Can you make a "find me a job" app? then I'd be impressed

First off this is an excellent piece of work. I do have a couple small problems though. Every time I unlock my screen I get a message telling me CPUBoost has been granted root privileges. Occasionally when I look at the widget, it's blank beyond displaying CPU temp. I can only get it to display info if I reopen CPUBoost and redo my settings.

Conap,
You mentioned letting you know about running this on other platforms. I loaded CPUBoostLite and it locked it up at 748MHz and 729MHz almost immediately. Had to do a battery pull both times.
ROM: NonSensikal 15.2
Launcher: ADW (Force closes)
SA Governor
I have run SetCPU at these speeds with no issues.
Hope this helps. You do great work.
Took a break from CELB for a while but will return shortly.
Thanks for your support. You too Tazz and Workshed.

gospodinwizard said:
First off this is an excellent piece of work. I do have a couple small problems though. Every time I unlock my screen I get a message telling me CPUBoost has been granted root privileges. Occasionally when I look at the widget, it's blank beyond displaying CPU temp. I can only get it to display info if I reopen CPUBoost and redo my settings.
Click to expand...
Click to collapse
You should see the message pop up when unlocking your phone if you have a screen off profile set. Are you using a screen off profile? Thanks for the feedback on the widget. I am trying to avoid having the actual widget poll the app for the info cause I am attempting battery friendly widget there but unfortunately if the data disappears for some reason then like you said it stays blank till the settings are reapplied. Thanks for the feedback. I will look more into that.
nagahtom said:
Conap,
You mentioned letting you know about running this on other platforms. I loaded CPUBoostLite and it locked it up at 748MHz and 729MHz almost immediately. Had to do a battery pull both times.
ROM: NonSensikal 15.2
Launcher: ADW (Force closes)
SA Governor
I have run SetCPU at these speeds with no issues.
Hope this helps. You do great work.
Took a break from CELB for a while but will return shortly.
Thanks for your support. You too Tazz and Workshed.
Click to expand...
Click to collapse
Actually when I said other platforms I meant like 2.1 but all feedback is appreciated. I'm not sure why it would lock up at those speeds if it doesn't with other apps. You have run setcpu at those speeds with your current setup? ADW force closes? is that when you use the app or when you set it too high? Thanks again for the testing....

Conap,
I'm running setcpu at 748 now with no issues. I didn't have setcpu installed when I tested CPUBoostLite. With CPUBoostLite installed, when the screentimeout fired off and brought up the lockscreen I tried to go back in and it wouldn't let me open the homescreen, everything is frozen and there is an FC msg for ADW. Maybe it just doesn't play very well with the current version of ADW. BTW, I'm not complaining. I think CPUBoostLite is a great idea. Hope this helps and as always, thanks for all the hard work you've put into your ROMs.

[APP] DHD Proximity Sensor Recalibrator 1.10 (26-Sep-12)

Due to many DHD's being incorrectly factory calibrated with regards to the proximity sensor, I wrote a little app to allow one to change the calibration on-the-fly and persist it over reboots.
This app is specifically for those experience issues with the proximity sensor.
Well known symptoms include the following:
- Screen fails to turn off when holding to face on a call
- Screen does turn off when holding to face on a call, but fails to come back on, requiring taking out the battery
These problems are common in custom kernels/ROM's. HTC has addressed this issue however in their kernels from 1.32 onwards, but have failed to provide an acceptable solution for some.
I present DHD Proximity Sensor Recalibrator. Download from the attachments below.
Here are some 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"
}
Usage:
1. Install app.
2. Run app.
3. Press the toggle button to start monitoring.
4. Move your finger over the proximity sensor (the little LED next to the front facing speaker).
5. Adjust the High and Low threshold values to your liking.
For those whose screen does not turn off, it probably means the factory values are set too high.
For those whose screen does not turn back on, it probably means the factory values are set too low.
The setting will be saved, and will be applied every time you reboot your phone. No need to go through any of the steps unless you want to change the calibration. When the settings are applied at boot time, you will get a toasty indicating the calibration value applied.
Possible calibration procedure:
1. Put both values high (will show FAR).
2. Cover sensor with finger.
3. Lower High threshold till it says NEAR.
4. Lower Low threshold by a notch or 2.
5. Test behavior
Removal:
If for whatever reason you find the application does not work, or you do not want it anymore, just uninstall the app, and reboot. Your original factory settings will be in effect again. This application does not modify your system. It might require root rights.
Source code repo:
https://github.com/leppie/DHD-Proximity-Sensor-Recalibrator
Known issues:
- Permissions have changed in CM7 RC2, preventing the application from working correctly. The application will need root. Will investigate how to add that, if needed.
- Some reports that the Gingerbread leaked ROM is not working.
Gingerbread/newer kernel update:
Due to changes in the source code made by HTC to overcome this issue in the kernel, this app will probably not run correctly.
There are 2 problems (as found from latest CM kernel source):
1. When the kernel recalibrates the proximity on the fly, it fails to update the internal structures in the kernel. This makes the kernel not report correct values. I have made a kernel patch to rectify the issue. Please ask your kernel developer to apply the following changes: https://github.com/leppie/htc-kernel-msm7x30/commit/b1d0a85f3fe5252c8ab43ba98261bcb1b8498d8a
2. Secondly and more seriously, depending on the initial calibrated value (if LT is greater or equal to 0x50), the kernel will kick off a polling thread. This will overwrite the changes made by this app, as soon as you use the proximity sensor for the first time (eg the phone). Afterwards you can apply the values from this app again, and from my experiments the value sticks then (up to the next reboot). Unfortunately, this polling mechanism fixes the issue for most users, so it cannot just be disabled. It is easy to disable in the kernel source however, but will probably break most other people's proximity behavior if they do not have this app installed. As you can see, there is not much I can do about this. The best option is to compile your own kernel.
Manual cleaning of the sensor:
After time the sensor will become dirty from the environment. See http://forum.xda-developers.com/showpost.php?p=28495941&postcount=357 for details on cleaning it.
Please report any bug and suggestions.
Cheers
Revisions:
1.0
- Initial public release
1.1
- Replaced toggle button with normal one to resolve known issue
1.2
- Removed amount from Paypal, feel free to donate whatever you feel like. Beers are around US$2 here.
1.3
- Add some better handling when something goes not as planned (likely on non-DHD hardware).
1.4
- Added some alert dialogs to aid with the problems people are experiencing. (In case of error, please note both the title text, and the first few lines in the text of the alert dialog.)
1.5
- Only for CM7 users. Use nightly 92 or above. This includes the necessary kernel patch.
- Should work on SENSE with custom kernel. Apply this patch (or ask your kernel 'builder' to do so).
- Removed Beer button due to crappy paypal policy...
1.6
- Added support for calling 'su' when permissions are wrong. Thanks VampireWicked.
1.7
- Correct boot permissions for ICS
1.8
- Prevent app from being installed on SD card (which will cause issues) (thanks makarand14)
1.9
- Fix issues with sensor listener not getting disabled (thanks Roberto_Lim and Stoffl_)
1.10
- Fix issues with slow process manager in Android, notably in BlackOut ROM (thanks tonylee000 and others)
Supported kernels:
- CM7 nightly #92 or later
- LorDModUE V2.6 or later

great .. gona try this now ..!!

Simply works. Great job!

jkoljo said:
Simply works. Great job!
Click to expand...
Click to collapse
how do you get it to work? when i move my finger over the sensor nothing happens. it always says near?

Them you have to change the settings. The app works great btw!
Sent from my Desire HD using XDA App

If it says near, make your values higher.
In a bad case, keep your finger over the sensor, and then increase the low threshold till it changes.
Then work from the settings there.

Awesome!
This is my favorite app to date! I couldn't use any Cyanogen mod because of this issue. (My device was not waking up after the first phone call) Everything else worked fine.
Now I can use my phone as a phone too!
Would recommend to any O2 Germany DHD user having similar issues.

Stuclint said:
This is my favorite app to date! I couldn't use any Cyanogen mod because of this issue. (My device was not waking up after the first phone call) Everything else worked fine.
Now I can use my phone as a phone too!
Would recommend to any O2 Germany DHD user having similar issues.
Click to expand...
Click to collapse
Yep i'm O2 Germany DHD user too and had this issue.
This is really a life-saver app, thanks!
You are awesome, leppie!

I didn't even have a problem with my sensor, but I tuned it a little bit anyway. Awesome. THANK YOU

Thanks man! Helped me a lot!
Burkow

I had this sensor problem and did make enquiry in other thread but can't find anysolution.
However, (don't konw since when) it works without any problem now.
Guess I should subscribe this thread just in case I need it in future (hopefully not).
Thanks leppie!
5 stars rated.

Thanks for all the complements.
Added a link to the public source code repository on github.com for those interested.

Hi!
hi!! does anyone know about this app but for the HTC HD mini?
thanks!!!

boxer39 said:
hi!! does anyone know about this app but for the HTC HD mini?
thanks!!!
Click to expand...
Click to collapse
Sorry, that is a Windows Mobile phone. Can't help with that

Thank you guy!! Finally!! Great work

Ace app! Even though I'm on stock, I sometimes get problems with my screen coming on during a call, and my accidentally muting the call. This should help me fix it, by fixing the threshold distance!
Awesome, thanks

leppie said:
Sorry, that is a Windows Mobile phone. Can't help with that
Click to expand...
Click to collapse
it's ok, this thing is killing me!! I just didn't find a buyer yet, but i'm definitly changing it for the desire HD! the best one!!
thanks!!!

T-Mobile G2
hey
will this work on the T-Mobile G2 (Desire Z). If so I will be SOOO grateful to you and I probably will actually buy you a beer. My girlfriend and I both have G2's and the proximity sensor is the only problem with these phones.
Dave

hi,
i have both sensor problems! every second time my phone turns off the screen while phoning but not on again or somtimes the sreen is still on while phoneing
with the app i can set the sensor but still not working during a call
can someone help me?
sry for my bad english

Thank you. Will try it on my Desire HD later

[APP] [9/7] Proton Voltage Control v1.3 | Easy UV for Netarchy and Matr1x Kernels

{
"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"
}
Version 1.3 [Released 9/7/11]​
Proton Voltage Control is an easy to use app that allows you to set custom voltages for Nexus S phones running a supported version of Netarchy and Matr1x kernels (1.3.0.6 for Netarchy and 4.0 for Matr1x and up) This means you no longer have to muck around with command line codes and scripts, just one easy to use app!
I am a busy highschool student, with no solid income. If you like my app, please consider a donation
Click to expand...
Click to collapse
Downloads
Update 16/9/11: Due to requests, I have built 1.3 again but with a different release key. Please UNINSTALL any old version before installing!
Version 1.3 ProtonVoltageControl-130.zip
Emergency Restore: proton_emergency_boot.zip
Usage
Enter in your new voltages in the 8 text boxes, or use one of the 3 buttons at the top to give you a base to try.
Hit Apply to set temporarily, and see how the voltages perform. If you reboot at this stage, the new voltages will be lost
If these new voltages work well on your phone, enter them in again and this time check 'Save on Boot' then hit Apply. These voltages should be applied upon startup every time now
Easy!
- It is easier to press one of the 3 voltages buttons to give you a base to work on
- The suggested voltages is mostly -20mV on all frequencies (from stock voltages) except for 1.4ghz and 1.3ghz which have been raised ever so slightly
- 'Save on Boot' creates an init.d script called proton_voltage_control with your entered values, so don't be alarmed if you see an extra init.d script
- Press Menu and Emergency Boot Zip to download a flashable update.zip to remove any 'Save on Boot' files in case you can't boot up due to setting the voltages too low. Boot into Recovery and flash like any other update.zip
Enjoy! Please ask if you have any questions, I will try to help with them. Standard disclaimer applies, I claim no responsibility for anything that goes wrong with your phone due to misuse of this app.
Also on the Market! https://market.android.com/details?id=com.jonathongrigg.proton.voltagecontrol
Proton Voltage Control is fully open sourced
Source is available at my Github, https://github.com/jonathongrigg/ProtonVoltageControl
Credits
Jonathon Grigg
Spiicytuna [New UI overhaul]
Xan [Original Galaxy S app which gave me inspiration to write my own from scratch for the Nexus S]
'Serge' (from MarketEnabler I believe) [ShellInterface code]

Donators
Tord Persson
Should work on all Nexus S models (including the 4G)
Sent from my Nexus S

Can I request custom settings save profile? In case something doesn't work you might want to go back to a profile and change things around.

Using it, and loving it so far
Sent from my Nexus S using XDA App

Good App. I will buy Pro Version if you publish one in the market.
Sent from my Nexus S using XDA Premium App

Had been using script manager with custom scripts to get settings loaded on boot, but have deleted them to use this
Really like the app, can't wait for UI improvements (even though it is fully working now).
Get this thing on the Market with a pro version!
Edit: Jonathon, maybe you could go in depth a tad more on usage , just for the moment because people new to UV may be confused what it does and how it works exactly

thanks dude, it's awesome! I've been waiting for an app like this to UV netarchy's kernels!
i'm running CM 7.0.3 with netarchy's 1.3.2, just did a -50mV across all frequencies and it has been working very well.

Please forgive my ignorance... but what exactly can be obtained by altering voltages??
Better battery life etc?

Thanks for the UI for UV'ing! It makes life so much more easier than typing on terminal.
One concern though, my settings are not saving on reboot. I'm running SuperAOSP 8.0 with Netarchy 1.3.0.12 CFS 2.3.4 Universal and after entering my desired values and checking Save on Boot, upon restart the app reads back the default voltages again (1450 etc...).
The program does state that it saves it to init.d but other than that it doesn't save it. Am I doing something wrong or am I supposed to re-enter values everytime i make changes to my phone that requres a reboot, which is a lot considering i try out a lot of the ROMs out there often.

Dario777 said:
Please forgive my ignorance... but what exactly can be obtained by altering voltages??
Better battery life etc?
Click to expand...
Click to collapse
Better battery life and lower temperatures.
Sent from my Nexus S using XDA Premium App

jello24 said:
Thanks for the UI for UV'ing! It makes life so much more easier than typing on terminal.
One concern though, my settings are not saving on reboot. I'm running SuperAOSP 8.0 with Netarchy 1.3.0.12 CFS 2.3.4 Universal and after entering my desired values and checking Save on Boot, upon restart the app reads back the default voltages again (1450 etc...).
The program does state that it saves it to init.d but other than that it doesn't save it. Am I doing something wrong or am I supposed to re-enter values everytime i make changes to my phone that requres a reboot, which is a lot considering i try out a lot of the ROMs out there often.
Click to expand...
Click to collapse
Do you have super user set up properly? Clear permissions from the app and try again
Sent from my Nexus S using XDA App

Thanks for this. Great app, makes it very easy.
Sent from my Nexus S running NSCollab, Cyanbread Theme and OC'd to 1.2ghz (Perfection)

Great app! Definitely saves time when tinkering with the voltages.. Thanks!

Has anyone tried this with default kernel from superaosp 8.2? It looks very similar to netarchy....
Also any recommendations for voltage levels?
Sent from my X10i TripNMiUI-IRIS using XDA App

can you add support for trinity kernels?

shubu000 said:
Has anyone tried this with default kernel from superaosp 8.2? It looks very similar to netarchy....
Also any recommendations for voltage levels?
Sent from my X10i TripNMiUI-IRIS using XDA App
Click to expand...
Click to collapse
Voltage levels will depend on individual phones, some will go lower while others would bootloop so low (good idea to not use set on boot to start with until you've tested it for a bit). There is a suggested voltages button in the app which is -25mV across all 8 frequencies as a starting point. Most phones should be able to handle this, but there are a few exceptions.
Sent from my Nexus S

The only two reasons why you would want to decrease or under volt (UV) set your frequencies is to save battery and extend your processor life expectancy.
The only reason to to increase or over volt (OV) your frequencies is to get a higher clock speed on your processor. Some phones will not handle the default setting and need extra voltage for transistors to get a better and cleaner signal.
This is very much the same principle as in any desktop PC. You increase voltage to be able to overclock but if you have a good quality fabrication, ie later production processor or maybe manufactured in a different fabrication facility you might be able to get away with less voltage which in effect lowers your battery usage. You could also achieve the same by better cooling, but unless you expect to keep ice on your phone, this doesn't really make sense.
To dig deeper into the matter, as far as I understand, when higher clock speeds are requested of a processor, transistors give away more heat. This in turn will also swell them up and they will start to short from one to another and/or loose current flowing through them. Another effect is the slowing down of the transistor gate on/off. All these conditions may trigger an error and in some cases a major freeze of the processor.
There... a quick explanation to have this app available.
BTW, we should also thank Netarchy for making such settings available in his kernel. Cheers

jello24 said:
Thanks for the UI for UV'ing! It makes life so much more easier than typing on terminal.
One concern though, my settings are not saving on reboot. I'm running SuperAOSP 8.0 with Netarchy 1.3.0.12 CFS 2.3.4 Universal and after entering my desired values and checking Save on Boot, upon restart the app reads back the default voltages again (1450 etc...).
The program does state that it saves it to init.d but other than that it doesn't save it. Am I doing something wrong or am I supposed to re-enter values everytime i make changes to my phone that requres a reboot, which is a lot considering i try out a lot of the ROMs out there often.
Click to expand...
Click to collapse
bringonblink said:
Do you have super user set up properly? Clear permissions from the app and try again
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yeah SU was set up to allow the UI to work, but I cleared that permission and ran the program again allowing it to go but it still won't save on boot. Existing voltages always show the default, instead of my desired settings.
I even tried it where i'd have to keep clicking allow on SU to get it running but it still won't save.
any other suggestions?

jello24 said:
yeah SU was set up to allow the UI to work, but I cleared that permission and ran the program again allowing it to go but it still won't save on boot. Existing voltages always show the default, instead of my desired settings.
I even tried it where i'd have to keep clicking allow on SU to get it running but it still won't save.
any other suggestions?
Click to expand...
Click to collapse
Can you try the 'cat' command to list the voltages in Netarchys thread and see if its the same as the existing voltages shown in Proton.
Sent from my Nexus S

jello24 said:
Thanks for the UI for UV'ing! It makes life so much more easier than typing on terminal.
One concern though, my settings are not saving on reboot. I'm running SuperAOSP 8.0 with Netarchy 1.3.0.12 CFS 2.3.4 Universal and after entering my desired values and checking Save on Boot, upon restart the app reads back the default voltages again (1450 etc...).
The program does state that it saves it to init.d but other than that it doesn't save it. Am I doing something wrong or am I supposed to re-enter values everytime i make changes to my phone that requres a reboot, which is a lot considering i try out a lot of the ROMs out there often.
Click to expand...
Click to collapse
I think I might know what your problem is. You have to hit apply after you select set on boot, otherwise it won't save the changes.
I didn't realise this the first time either!!!