Database Info

iGo8 Custom Startup and Background

I wanted to share this information. I recently was able to change the loading screen and add backgrounds to iGo8(I know I'm not the first one). Thought I would share what I did in case anyone else is interested. Also, have attached a screenshot of the startup screen I used(there is also a matching background to tie it all in). Also attatched is my "branding.zip" file and zip with 240x320 background.bmp/loading.bmp. If you like what I did you can just use mine. This is for 240x320 and 320x240 qvga sizes only(I deleted all other files). Follow link for "data.zip".
Here is what I did:
1.) I did a google image search and found a picture that I liked. Downloaded and saved as a bitmap file
2.) Resized the picture to 240x320. This would depend on your screen size.
3.) Made a copy and named it "loading.bmp"
a.)Optionally, I used photo software to add the iGo logo ( I used pocket artist)
4.) Copied "data.zip" and "branding.zip" to my computer (Keep a backup copy)
5.) Using winRAR, I opened "branding.zip" and found \ui_igo8\240x320 and added "loading.bmp" to the archive overwriting the original "loading.bmp"
6.) Using winRAR again, opened "data.zip" and found \ui_igo8\240x320\background
a.)added my resized bitmap image to this folder(named mine "blueflames.bmp")
b.)while I was at it, I got rid of everything I didn't need such as backgrounds and other files for screen sizes I did not need. Went from 12mb to 5mb(saving all the room I can)
c.)have read that this can be done alternately by adding folders "ui_igo8\240x320\background" to the "igo8" folder on sd card. This did not work for me.
7.) Copied "data.zip" and "branding.zip" back to sd card overwriting the originals(make sure to keep copies just in case, something I forgot to do)
8.) Abracadabra when you start iGo8 you get a fresh new loading screen and background
{
"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 searched for a place to post this but did not find what I was looking for. If I'm in the wrong place let me know, move it, remove it, or just shoot me.
As I said before, I know I'm not the first to figure this out. And I'm in no means a genius or programmer. I was so happy the first time I started iGo8 up and saw my own screens that I had to share with somebody. Let me know if I can help with anything(to the best of my ability). Let me know if I missed something.
NOW WITH LANDSCAPE:Slight change on landscape as could not resize without distortion. Turned original background and splash.
data.zip http://www.4shared.com/file/68709169/ea33cfb2/data.html

More iGo info
Just something else I have found. My iGo was taking forever to load, so I removed some of the custom poi's that I had as well as everything else I did not need(other states, poi's from other states) and stored them on my computer. When I need them, I can put them back.
Since doing this, it now loads just as fast as TomTom7(if not faster). Just in case anyone is interested.

Matching Splash for Opera Mobile
Here's a matching splash screen for opera mobile for anyone that likes the blue flames and wants everything to look alike. Unzip "opera_splash.zip" into \program files\opera9 overwriting the existing files. Make a copy of existing files first in case you want to revert back to original without reinstalling.
​

Loading.bmp fails to load, Igo8 aborts
Hi,
Using the information in this thread, I tried to replace the bitmap used during loading and as background. My bitmap works very well as background, but during loading I get an load error message.
Looking at the original loading bitmap, I found that the file is 2 bytes longer than it normally should be. 320 * 240 * 3 + 54 ( bitmapfileheader and bitmap informationheader) = 230454, whereas the actual file size = 230456.
A program like Windows Viewer displays the original file correctly, as it does with my own files.
Also the blueflames bitmap fails to load.
I use IGO8 8.0.035389.
Does somebody have an idea what is going wrong?
Harry

May need update
I am using an updated version 8.0.0.49545 which may explain the difference. Do you have access to the content manager which allows you to get updates? There was a bug fix in the september release that could help. Also, what device are you using? If you dont have access for updates, PMme and I can direct you to an updated version. Make sure your image is the correct size, make sure you convert to bitmap and not just change name. I think I just used MSPaint to open my jpeg and saved it as a bmp. I'll try to do what I can to help. Ijust assumed since it worked great on my device it would be universal. You didnt change anything else in branding.zip?

Loading bitmap problem
Hi,
My PDA is a MIO P350. My bitmap is really a Windows bitmap. Note, that also blueflames didn't load. No other changes were made to Branding.zip. Please send me the update.
Harry

in sys.txt you can add
[loading]
show_statustext=1
show_progressbar=1
progressbar_x=85
progressbar_y=120
loading_bmp="loading.jpg"
make sure a loading.jpg that fits your screen size is placed in
data.zip\ui_igo8\320_240 further since show_progressbar is enabled ( =1)
a loading_progress_bar.bmp is needed in data.zip\ui_igo8\320_240
This worked with igo 8.3xx

"Failed to open file"?
Dear mates,
When I switched to iGO 8.3.4, copying the Data, BRANDING and SYS files to my SD card, I got the error message on start: "Failed to open file: igo\800_480\loading.bmp. Exiting application."
Still when I am using the new files except the data.zip(using my old data.zip - from iGO 8.3.2 I had) the program is OK. But when I try to use the new data.zip - the program crashes with the error above ?
Please help !
Best Regards

Hi jmckeejr, hi mates,
I tried to change the loading picture too with a car logo but it did not succeed. I downloaded your branding file and it works flawlessly, however, I already use iGO 8.3.4.117940.
Then I tried to do this: opened the branding.zip, changed the loading.bmp to mine and compressed it again, copied it back to the device, but it doesn't recognize the file, loads with a grey road-like image. Could somebody help me to get a car logo to work? I made these steps with the original branding file and with yours too.
Thx
as

start screen for Igo 8.3.4
For Igo 8.3.4 it doesn't work that way, changing the splash screen for 240x320 portrait resolution actually goes like this:
1. leave data.zip and branding.zip as they are and just create a new folder in the igo root folder and name it "ui_igo8" (usually it doesn't exist)
2. create a new subfolder in the new created folder "ui_igo8" and name it "240_320"
3. Create a loading.jpg file with 240x320 resolution - any photo editor is good, and put it in the SD/Igo/ui_igo8/240_320
4. create a loadingprogressbar.jpg that looks like a ribbon with a resolution of 120x10 (or search one on google)
5. write in your sys.txt file found on the Igo root folder the following lines:
[loading]
show_statustext=0
show_progressbar=1
progressbar_x= 130
progressbar_y=230
loading_bmp="loading.jpg"
loading_progressbar="loadingprogressbar.jpg"
6. turn on IGO and after splash screen is shown you will figure out what the loading bar position is, if needed just adjust its location changing the progressbar_x and progressbar_y values in sys.txt
Here is an archive http: // tinyurl.com / 3ejnedt with needed folders and files, just copy it on your Igo root folder and extract everything there.
Hope it helps!
I didn't figure out how changing the exit splash screen (which is the same with the original start splash screen) works, if somebody knows lets hear it!

[PC-APP] Tweaking your X10 Equalizer

{
"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"
}
Android allows for customization of 8 bands of sound, each with individual values for gain, frequency range, type and qf. The EQ settings is disabled per default in our X10s, and this and more information is stored in a file called AudioFilter.csv (/system/etc/).
I wrote a handy little JAR-application that helps you edit this file and save a new copy on your PC. With our new found root privileges, this can then be pushed to device and overwrite the existing settings, modifying your X10's sound levels as you see fit.
As the /system/ parition is mounted as read-only filesystem, we can't simply push files straight to /system/etc. Therefore we will push the file to the /sdcard/ and, remount the partition as read-write, and then use the superuser privileges to copy the file over and replace the existing one.
Start by editing the AudioFilter.csv. Here is a copy of the original X10 settings file (Download: MegaUpload, MediaFire). Open it in the app, and edit it to your liking. Then save it as a new copy and follow the instructions below on how to replace the current settings. To enable the EQ, set "Enabled" value to 'FFFF', and then play with the bands' individual values. When you have the EQ set, move on to the step by step instructions:
1. PC: "adb push AudioFilter.csv /sdcard/
2. PC: "adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system"
3. X10: "su"
4. X10: "cp /sdcard/AudioFilter.csv /system/etc/"
5. X10: "reboot"
And there you go, your settings should be changed after boot. I am new to Android, so please correct me if I am completely lost on the matter.
This is not yet working, so no need to download yet - if you don't want to help out of course!
Download: MegaUpload, MediaFire
Please do not redistribute or mirror this application without my concent.

Reserved for future usage.

Looks like good work.

You know Java, we have root, why not making an android app to do just that?
What's the point of running commands when you can do it directly from an app?

oh, it's geat idea to put EQ into X10 !! But has anyone tested?? Plz do android app and clear tutorial how to .....

tuxStyle said:
You know Java, we have root, why not making an android app to do just that?
What's the point of running commands when you can do it directly from an app?
Click to expand...
Click to collapse
Yes, that would naturally be the next step. I just wanted to see if people found this useful at all first..?

If there were an app for this, i would be the first to DL it

Has anyone tried this yet. I'd love to try it, but not sure how the values work, within the program :/

It maybe worth listing what each of the bands do and also what codes to use to increase the volume or decrease the volume.
This may also be useful
http://forum.xda-developers.com/showthread.php?t=517745

This is F****in pro!! Thank you , and this is very useful, an app would be even better but I'm happy as is
Edit: Do you have a link to explain the freq codes?

I don't understand instruction how to apply the equalizer, I havent also my x10 rooted but I will do.... could anyone do instructions how to instal the eq, step by step?????
Sent from my X10i using XDA App

@karooluss
Download both links, Mr Rusch's csv, and x10 EQ. Open eq, hit open file, find csv you downloaded. To apply follow the script on the first page.

AndyD777 said:
It maybe worth listing what each of the bands do and also what codes to use to increase the volume or decrease the volume.
This may also be useful
http://forum.xda-developers.com/showthread.php?t=517745
Click to expand...
Click to collapse
If I may assume this works like any other normal EQ: The bands themselves are not controlling different things as someone said here before, but rather different frequency ranges. So basically, per the default settings - band1 are the very lowest of frequencies (most probably rumbling "bass" sounds), and band8 are the highest (sounds we can probably not even hear). I will try to explain it part by part..
Gain: This is volume increase/decrease, normally measured in dB.
Freq. (Frequency Range): This is the peak of the frequency range, which together with Type and QF determines the effect on the sound curve.
Type: This is the type of filter used on this frequency range. I believe 1 represents a lowpass filter, 2 a highpass filter, and 3 a notch filter. There may be more types, I don't know.
QF (Quality Factor): This is, simply put, the width of the curve in this frequency range. A low QF usually affects a wide frequency range, and a high QF usually a narrow one.
As for the values used, these are all half a byte of hexadecimal. 0 is zero, or null. FFFF is max, and would in decimal represent 65535. So, the frequency values used by standard (from band1 through 8) are 400, 500, 2000, 4000, 5000, 8000, 9000, 18000 in decimal, and probably actually a Hz value.
So, the values you enter have to be in HEX. Use a decimal to hexadecimal converter if HEX values are completely foreign to you.

app please! great job man

Have you tested this on your own handset?

AndyD777 said:
Have you tested this on your own handset?
Click to expand...
Click to collapse
Of course, wouldn't post it here otherwise. Haven't had time to find good levels yet tho. Maybe you guys can help out.

MrRusch said:
Yes, that would naturally be the next step. I just wanted to see if people found this useful at all first..?
Click to expand...
Click to collapse
You are kidding?
How many audio players out there have an EQ?
This one would help a lot.

@mrrusch
Thanks for the update on how to use but one more question (it may be dumb) does changing the number in enable have any effect? I also turned the qf to 500. It seems like mp3s are a bit clearer but i cant hear a difference in wav files. Im using westone 3s no amp
Sent from my X10a using XDA App

gavriel18 said:
@mrrusch
Thanks for the update on how to use but one more question (it may be dumb) does changing the number in enable have any effect? I also turned the qf to 500. It seems like mp3s are a bit clearer but i cant hear a difference in wav files. Im using westone 3s no amp
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Enable needs to be set to either 0 or FFFF (0 = off, FFFF = on). This toggles whether to use the EQ or not.

When opening the original enable is set to 0. Therefore its turrned off. If we turn it on and save it. Would we ntice any difference?

[GUIDE] how to make a bootanimation

I posted some of my boot animations (in true qHD) in another thread for the HTC Sensation and got a PM about how I did it. So here is my work flow:
you will need
1) Handbrake http://handbrake.fr/downloads.php/
2) ffmpeg http://ffmpeg.zeranoe.com/builds/
3) winrar http://www.rarlab.com/download.htm
1st set-up
1) download and install handbrake AND WinRar
2) make a directory c:\ffmpeg
3) download and copy the ffmpeg.exe into c:\ffmpeg
4) make this batch file and save it as c:\ffmpeg\convert.bat:
Code:
cd c:\ffmpeg
mkdir c:\ffmpeg\part0
ffmpeg -i c:\ffmpeg\in.mp4 -r 23.98 -vf transpose=1 -qscale 15 -f image2 c:\ffmpeg\part0\frame_%%05d.jpeg
ping 192.168.255.255
a guide:
qscale = 1 is highest quality jpeg setting conversion and will give you largest file size, 30 is worst quality.
transpose = 1 rotates the video so it is landscaped correctly on the screen
r = frame rate, most things are ~24 fps
5) make this batch file and save it as c:\ffmpeg\pack.bat
Code:
cd "C:\Program Files\WinRAR"
winrar.exe a -afzip -r -m0 -ep1 c:\ffmpeg\TMOUS_bootanimation.zip c:\ffmpeg\desc.txt c:\ffmpeg\part0
ping 192.168.255.255
6) make this text file and save it as c:\ffmpeg\dec.txt
Code:
540 960 24
p 1 0 part0
change the 24 to your frame rate if the source video / ffmpeg processing was at a different frame rate.
Usage:
1) Get your video and process it through handbrake....
Convert it to an .mp4 video and crop/adjust so it is true qHD, then convert.
2) play the video in (VLC) to check it is ok
3) and check that the resolution is exactly 960 horizontal x 540 vertical.
4) save/copy the video as c:\ffmpeg\in.mp4
5) run convert.bat
you should now have a directy c:\ffmpeg\part0 full of rotated jpegs 540 horizontal x 940 vertical.
At this point you can delte jpeg (sequences) you don't want and also check the length. Most boot animatisn need to be <45 seconds so 24x45 = 1080 jpegs is all your resonably shoudl leave in your part 0 directory.
6) run pack.bat
you will now have a c:\ffmpeg\TMOUS_bootanimation.zip ready to copy to the system partion of your phone. Dont forget to backup the ld one and match the correct r/w permisions.
good luck!
I have attached my working directory, including ffmpeg and the batch files etc.
Enjoy! :good:

Dang I am out of thanks for today man. But thanks a bunch for this tutorial man it is awesome, I will definitely be using it. You might want to contact the OP of this thread and see if he wants to add a link to your thread here in his thread.

htcsens2 said:
I posted some of my boot animations (in true qHD) in another thread for the HTC Sensation and got a PM about how I did it. So here is my work flow:
you will need
1) Handbrake http://handbrake.fr/downloads.php/
2) ffmpeg http://ffmpeg.zeranoe.com/builds/
3) winrar http://www.rarlab.com/download.htm
1st set-up
1) download and install handbrake AND WinRar
2) make a directory c:\ffmpeg
3) download and copy the ffmpeg.exe into c:\ffmpeg
4) make this batch file and save it as c:\ffmpeg\convert.bat:
Code:
cd c:\ffmpeg
mkdir c:\ffmpeg\part0
ffmpeg -i c:\ffmpeg\in.mp4 -r 23.98 -vf transpose=1 -qscale 15 -f image2 c:\ffmpeg\part0\frame_%%05d.jpeg
ping 192.168.255.255
a guide:
qscale = 1 is highest quality jpeg setting conversion and will give you largest file size, 30 is worst quality.
transpose = 1 rotates the video so it is landscaped correctly on the screen
r = frame rate, most things are ~24 fps
5) make this batch file and save it as c:\ffmpeg\pack.bat
Code:
cd "C:\Program Files\WinRAR"
winrar.exe a -afzip -r -m0 -ep1 c:\ffmpeg\TMOUS_bootanimation.zip c:\ffmpeg\desc.txt c:\ffmpeg\part0
ping 192.168.255.255
6) make this text file and save it as c:\ffmpeg\dec.txt
Code:
540 960 24
p 1 0 part0
change the 24 to your frame rate if the source video / ffmpeg processing was at a different frame rate.
Usage:
1) Get your video and process it through handbrake....
Convert it to an .mp4 video and crop/adjust so it is true qHD, then convert.
2) play the video in (VLC) to check it is ok
3) and check that the resolution is exactly 960 horizontal x 540 vertical.
4) save/copy the video as c:\ffmpeg\in.mp4
5) run convert.bat
you should now have a directy c:\ffmpeg\part0 full of rotated jpegs 540 horizontal x 940 vertical.
At this point you can delte jpeg (sequences) you don't want and also check the length. Most boot animatisn need to be <45 seconds so 24x45 = 1080 jpegs is all your resonably shoudl leave in your part 0 directory.
6) run pack.bat
you will now have a c:\ffmpeg\TMOUS_bootanimation.zip ready to copy to the system partion of your phone. Dont forget to backup the ld one and match the correct r/w permisions.
good luck!
I have attached my working directory, including ffmpeg and the batch files etc.
Enjoy! :good:
Click to expand...
Click to collapse
Hey man your a genius - I do most of this in After Effects and using Adobe Media Encoder but this is a much more original and inexpensive method Thanks for teaching me something new about video encoding!!!!

Thank you.
Sent from my HTC Sensation Z710e using xda app-developers app

Thanks for this guide really simple and usefull only thin I have is that my video is in landscape and I want in in portrait, how do I do that?
O and I don't end up with a packed zip file (only changed the directores of ffmpeg to d: and the Ip to my own)

Thanks for a great guide. This is so much better than the method I know which involves VirtualDub, TheGIMP and other costly software.

Rubman said:
Thanks for this guide really simple and usefull only thin I have is that my video is in landscape and I want in in portrait, how do I do that?
O and I don't end up with a packed zip file (only changed the directores of ffmpeg to d: and the Ip to my own)
Click to expand...
Click to collapse
I would use after effects and create a new composition in the aspect ratio you need. Of course not everybody has a copy of AE lying around... If you send me the video in PM with aspect you need i can do that for you - there will likely be some cropping

what to do next
did every thing as u listed but i get error about IN.mp4 saying permission denied ..
i also made directory named in.mp4 in the directory u suggested but still the same error have i done somthing..
firstly i maade all the .bat file
then the text file
converted a video in mp4
but when i run the convert.bat file it give me the error
{
"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 this guide man! I'll definately have a go at this!

I've made a simple script for flashing boot animation. The link is in my signature. Just drop the bootanimation.zip in the zip and flash it! As easy as that

[PATCH] True Tablet UI (Apps+GUI) w/o DPI Change for Stock & CM10 - Update Oct11 2012

[PATCH] True Tablet UI (Apps+GUI) w/o DPI Change for Stock & CM10 - Update Oct11 2012
Note: I am no longer maintaining releases due to time constraints. If someone would like to pick up the op, please pm me.
Recent Changes
10/11 - Updating CM10 nightly links - see next post
9/6 - Added nighly CM10 builds - see next post
8/1 - Cleaning to OP out a bit
Downloads
If you don't care about all the technical stuff, skip down to post 2 for downloads
Intro
Goal of thread is to share details around how the trigger for Phone UI/Phablet UI/Tablet UI works, and provide a dpi independent patch for tablet ui. Hopefully this also eliminates the misinformation that changing lcd density is the only way to get Tablet UI.
What's "true" tablet UI vs what is called tablet UI in many roms? The Tablet UI actually defines how some apps work (e.g. dual-paned settings like in the screenshots below) vs the other solutions that simply draw the standard Nexus UI with tablet navigation/system bars.
The 'Triggers'
In 4.1.x, there are two files that need to be modified:
PhoneWindowManager.java, located in frameworks/base/policy/src/com/android/internal/policy/impl contains the code that determines which UI to present. During compile this is a part of android.policy.jar
WindowManagerService.java, located in frameworks/base/services/java/com/android/server/wm contains code that specifies the lowest DP settings and has the system select from either sw600 or sw720 presentations. It is a part of services.jar
PhoneWindowManager
Click below for details regarding the source code to edit, and modifications for these releases
The source code calculates a value for shortSizeDP, and compares it to
shortSizeDP < 600 = PhoneUI
601 720
shortSizeDP is calculated as follows:
take the short size of the screen resolution (our screen is 1280x800, so use 800) * DENSITY_DEFAULT (a constant of 160) * LCD Density (ro.sf.lcd_density value in build.prop)
example: on stock: 800 (N7 short resolution) * 160 / 213 (stock lcd_density) = 600.9
since 600.9 > 600 but less than 719, we get Phablet UI
using 170 as ro.sf.lcd_density: 800 * 160 / 170 = 752.9
since 752 > 720 we get Tablet UI
this explains why the threshold on our device is between 177 and 178
original source code:
Code:
// SystemUI (status bar) layout policy
int shortSizeDp = shortSize
* DisplayMetrics.DENSITY_DEFAULT
/ DisplayMetrics.DENSITY_DEVICE;
if (shortSizeDp < 600) {
// 0-599dp: "phone" UI with a separate status & navigation bar
mHasSystemNavBar = false;
mNavigationBarCanMove = true;
} else if (shortSizeDp < 720) {
// 600-719dp: "phone" UI with modifications for larger screens
mHasSystemNavBar = false;
mNavigationBarCanMove = false;
} else {
// 720dp: "tablet" UI with a single combined status & navigation bar
mHasSystemNavBar = true;
mNavigationBarCanMove = false;
}
}
Modification
Given the code above, there should be many programmatic ways to force TabletUI:
Editing the values of 600 or 719, removing the Phablet UI mid section, or just commentting everything out and set mHasSystemNavBar = true; mNavigationBarCanMove = false;...and plenty of other options
Current Alphas are hardcoded to
Code:
mHasSystemNavBar = true;
mNavigationBarCanMove = false;
WindowsManagerService
Click below for details regarding the source code to edit, and modifications for these releases
Changing the values above we enough to try and force the UI to use tablet features, but since the Nexus 7 uses tvdpi (same as google TV when displaying 720p) with a fallback to xhdpi, SystemUI did not contain the requisite framework files (xml and pngs) and was force closing. Further, the sizing was mapped to the sw600 folders, which do not contain any of the tablet pngs/xmls.
Thus, we needed to edit the code that defined what the minimum screen size was to force apps to show in tablet form.
original source code:
Code:
private void computeSizeRangesAndScreenLayout(boolean rotated, int dw, int dh,
float density, Configuration outConfig) {
// We need to determine the smallest width that will occur under normal
// operation. To this, start with the base screen size and compute the
// width under the different possible rotations. We need to un-rotate
// the current screen dimensions before doing this.
int unrotDw, unrotDh;
if (rotated) {
unrotDw = dh;
unrotDh = dw;
} else {
unrotDw = dw;
unrotDh = dh;
}
mSmallestDisplayWidth = 1

Downloads
An now on to the part folks care about, please read the below in full
Credits:
I want to thank +aaronpoweruser, +lithium76, +cdesai for all their help and coding guidance; +Racer Of All for the zips; +the3dman for the Launcher2 fix, +z1gackly and +Nark.GA60 for their help with the CM10 patch, +Rsotbiemrptson for the odexed version
Disclaimer: I am not responsible for damaging your brand new nexus 7. Do not do this if you're not willing to brick it. Usage of the following files can cause a rift in the time-space continuum, the appearance of 20 foot android monsters in your town, turn your first-born into slime, change the gender of your significant other, tsunamis on mars, etc etc etc
Pre-requisites:
1. This is designed for Stock or AOSP JRO03D or Based CM10 (tested on Sep 6 nightly). Many folks are trying other roms that will either not boot or work. Please use the search above for your rom name before posting. Note: My development will focus on a patch to AOSP. I'm more than willing to work with devs on their roms, but the information above should suffice for them to bake the tweaks in however they want to.
2. You SHOULD BE DEODEXED. If you don't know what that means, then you likely aren't - so run a deodexer like mine or do it yourself . Update: Sept 7 - Rsotbiemrptson released a odexed version post 514
3. You MUST WIPE CACHE AND DALVIK. Formatting system and data/factory reset is not needed
READ BEFORE FLASHING List of Issues / Add Bug Reports:
Please report your issue here with all the information above.
https://docs.google.com/spreadsheet/ccc?key=0Aq1C5kjO0c_tdDFrbWVsOF9ROXJOblNFVzFYR29CQkE
Latest Downloads:
10/11 - CM10 Nightly - credits z1gackly and Nark.GA60 post 534
Download: goo.im
8/1 - Alpha 3 for STOCK ROM JRO03D: fixed launcher (patch Launcher2.apk), adds lockscreen rotation (patch framework-res.apk)
Download: Mirror 1 Mirror 2
Alpha3 creates a backup during install, restore using the following script: Mirror 1
Issues Resolved: Patched Launcher has huge borders on bottom/top fixed
Note: these new changes will likely cause compatibility issues with CM/AOKP roms and customized roms. Alpha 1 may be better for you
Reporting Issues:
Many people are not fully reporting problems. If I don't have enough details, then it's very hard or impossible to help.
Please provide:
Rom: (e.g. Stock version JRO03D, JRO03H, j5, etc) - this is found in system/about tablet
Kernel: stock or modified - this is found in system/about tablet (you will know if you modified it)
Issue Description: Exact issue, exact error message, steps to replicate, screenshot (power + vol down at same time) for visual issues. Words like 'many', 'a lot', 'often' are not helpful. If there were a lot of issues then it wouldn't have been released. If you are on another rom/kernel, please verify that any play store issues are not sourced by that rom/kernel combo first without the mod.
Bootloops, Crashes: I *need* a logcat - see my signature
Next Steps:
- Settings toggle (WIP)
- Hybrid UI (stock UI in portratit, tablet in landscape)
Prior Versions:
7/26 - Alpha 2 - thank you +Racer Of All
Download: Mirror 1 Mirror 2
MD5: 1c85cc5fe772f687ce9beaa8dab57130
Issues Resolved: credit the3dman - Stock launcher width is too long due to mods and cause overscan of ~half icon on either side. Use Apex, Nova, Go Launcher.
7/21 - Alpha 1 released - thank you again +Racer Of All
Download: Mirror 1 Mirror 2
MD5: dbf20c71544dc19ac87c5d59a03c6f12
Alpha 1 does make a backup of your original files, if something goes wrong, flash the zip below to restore the files:
Mirror 1 Mirror 2
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"
}

I hope someone runs with this. I'm running a tablet ui JB rom on my Fire and love it but I didn't want to screw around with dpi changes on the N7 that make everything smaller and bork the market.

just run the nova launcher

patterone said:
just run the nova launcher
Click to expand...
Click to collapse
Launchers allow homescreen rotation, which is NOT the same as tablet ui.

patterone said:
just run the nova launcher
Click to expand...
Click to collapse
tablet ui is more than just a launcher or rotation...it changes how apps interact with the system, e.g. dual-pane in settings

neilrl79 said:
I hope someone runs with this. I'm running a tablet ui JB rom on my Fire and love it but I didn't want to screw around with dpi changes on the N7 that make everything smaller and bork the market.
Click to expand...
Click to collapse
no clue where you heard it borks the market.. i am running 160 dpi and everything is perfect. 10x better than having a 7 inch galaxy nexus.

oasis9389 said:
no clue where you heard it borks the market.. i am running 160 dpi and everything is perfect. 10x better than having a 7 inch galaxy nexus.
Click to expand...
Click to collapse
Every thread that discusses dpi change to allow tablet ui also has people posting how some apps begin to show as incompatible after the change, that, imo,borks the market.

Would love to have a notification bar like the tablets do, the one they have now is ok, but I like the other one way better. Tried 160 DPI but it did not look good to me.

Holy cow what a stupid way for Google to determine which UI to display. Fixed:
Code:
// SystemUI (status bar) layout policy
if (layoutType == 1) {
mHasSystemNavBar = false;
mNavigationBarCanMove = true;
} else if (layoutType == 2) {
mHasSystemNavBar = false;
mNavigationBarCanMove = false;
} else {
mHasSystemNavBar = true;
mNavigationBarCanMove = false;
}
The alternative would be "screenSize"
Manipulating values, multiplying by meaningless constants and using values that are derivatives of the number that actually matters? Google's code was just stupid. Write the code so developers can tell it what they want, not so it enforces your recommended layout.

guys - kindly keep all lcd_density dpi discussion, complaints and issues to the existing threads in Q&A or general, so this thread can focus on code change development...the whole point of this thread is to offer an alternative to that already...thanks!

qoncept said:
Holy cow what a stupid way for Google to determine which UI to display. Fixed:
Code:
// SystemUI (status bar) layout policy
if (layoutType == 1) {
mHasSystemNavBar = false;
mNavigationBarCanMove = true;
} else if (layoutType == 2) {
mHasSystemNavBar = false;
mNavigationBarCanMove = false;
} else {
mHasSystemNavBar = true;
mNavigationBarCanMove = false;
}
The alternative would be "screenSize"
Manipulating values, multiplying by meaningless constants and using values that are derivatives of the number that actually matters? Google's code was just stupid. Write the code so developers can tell it what they want, not so it enforces your recommended layout.
Click to expand...
Click to collapse
that's the direction i was thinking as well - define a new global variable, and let devs build a toggle to set it into the settings (for user selection) or as a constant (if they just want their rom one way)

Actually, I think it probably makes even more sense to set mHasSystemNavBar and mNavigationBarCanMove independently of each other. This bit of code doesn't need to exist; these variables should be set wherever shortSize was set. So instead of choosing whether you have a tablet or phone, you choose whether you want each option enabled.

Can't wait for this!
Well done sir

If I was to make the change myself, can someone tell me what app(s) to use and just where framework folder is located? It does not seem to be in / using ES File Exp.
Thanks!

neilrl79 said:
Every thread that discusses dpi change to allow tablet ui also has people posting how some apps begin to show as incompatible after the change, that, imo,borks the market.
Click to expand...
Click to collapse
yea and my N7 is a paper weight b/c some guy has a picture of it laying on a magazine.. again i have been running at 160 for a day now with heavy use. i have 0 issues, i have installed all my apps, ran all my apps, all my widgets. i am on 160 you are not.
now i messed wtih 170 and 177.. yes those don't work well.. 160 is not 170 177
---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------
barrmulio said:
guys - kindly keep all lcd_density dpi discussion, complaints and issues to the existing threads in Q&A or general, so this thread can focus on code change development...the whole point of this thread is to offer an alternative to that already...thanks!
Click to expand...
Click to collapse
sorry just saw this.. carry on with the development.

oasis9389 said:
yea and my N7 is a paper weight b/c some guy has a picture of it laying on a magazine.. again i have been running at 160 for a day now with heavy use. i have 0 issues, i have installed all my apps, ran all my apps, all my widgets. i am on 160 you are not.
now i messed wtih 170 and 177.. yes those don't work well.. 160 is not 170 177
---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------
sorry just saw this.. carry on with the development.
Click to expand...
Click to collapse
That's freaking awesome for you bro! :good:
That being said, there are people who have had things go wrong after changing DPI to 160. Plenty of threads in General and Q/A detailing this.

bsw11 said:
If I was to make the change myself, can someone tell me what app(s) to use and just where framework folder is located? It does not seem to be in / using ES File Exp.
Click to expand...
Click to collapse
java file edits are made before they are compiled into files our phones/tablets use, there are plenty of great threads out there on building android

Nexcellent said:
That's freaking awesome for you bro! :good:
That being said, there are people who have had things go wrong after changing DPI to 160. Plenty of threads in General and Q/A detailing this.
Click to expand...
Click to collapse
"plenty of threads"
lol lord.. there is one topic on it.. a few posts of issues with people using other than 160. 160 works, end of story.

update on development
my nexus doesn't like the the android.policy.odex that i'm compiling from aosp, even without any changes to any of the files from the repo...it will just stay on the nexus X boot screen (after the Google bootloader) until i copy the original android.policy.odex back and then it finishes booting up within a few seconds
if anyone has succesfully built a mod or otapackage from aosp for grouper (i've been using full_grouper-eng), let me know if there were any special settings for compiling that are needed to get it to boot

How to Edit Frequencies in Exynos4412?

I've built a custom kernel for my Galaxy Tab 10.1 The link is in my signature. When I wanted to add custom frequencies to it, there was a very informative post that told me how to edit the frequency table to make the new clock speeds on tegra2 come out right and also how to edit the voltage tables. At least on the tegra2 it involved editing tegra2_clocks.c where you had to change the pll_x frequency table, change the pll_x max speed, virtual cpu max speed, sku max speed, and add an additional frequency table for your new clock speeds. The voltage was done in tegra2_dvfs.c where you added changed the min/max voltages accordingly and added in your new frequencies there.
I have looked all over the internet for a similar guide for my I9300. The cpufreq-4x12 looks nothing like the tegra one. It appears that every frequency has an entry in clkdiv_cpu0_4412 (for the S3 at least) with dividers for cryptic values like "divcore" "divcorem0". I've tried doing a grep search in the kernel source and couldn't find those names mentioned anywhere. There also appears to be another clkdiv_cpu1_4412 with even more cryptic values which don't appear in grep either. Then of course, there's yet another cryptic table that each frequency seems to go to called "apll_pms". It appears as the voltages go to the asv tables but how you accommodate new frequencies is beyond me. The L0,L1.. etc labels don't appear to follow the conventions stated earlier where 1800MHz is labelled L0 at the top but L-2 later.
I realize that many experienced developers probably take this information for granted and I wouldn't be asking for this if it was available somewhere else. The documentation folder in the kernel doesn't provide any information either.
Please help a startup enthusiast As a beginner, I've typically answered similar how to questions on my own thread in the beginning, when other people were interested in how to get their hands dirty with modifications. (Although now, people just seem to be interested in the final product which is fine too.)

Each divider value represents the real divider minus 1. So a value of 7 divides by 8. Populate the divider talbes with new entries like that. The registers have a limit so see the register maps in /mach/regs-clock.h. The dividers divide the final CPU clock. What values you give the dividers is up to you to decide.
The CPU clock is decided by the PLL as you saw. PMS decides the PLL frequency. The source quartz runs at 24MHz. The frequency is calculated by (P * Xtal) / (M << S).
Example 500MHz: ((125<<16)|(3<<8)|(0x1)), the format is ((P<<16)|(M<<8)|(S)).
(P * Xtal) = 125*24 MHz = 3000MHz
(M << S) = 3 << 1 = 6
End result is 3000MHz / 6 = 500MHz.
That's all you need to know. Alternatively, just copy what other devs have already done. Be careful with the Lx levels when you add new ones, you need shift all the existing ones throughout the file.

AndreiLux said:
Each divider value represents the real divider minus 1. So a value of 7 divides by 8. Populate the divider talbes with new entries like that. The registers have a limit so see the register maps in /mach/regs-clock.h. The dividers divide the final CPU clock. What values you give the dividers is up to you to decide.
The CPU clock is decided by the PLL as you saw. PMS decides the PLL frequency. The source quartz runs at 24MHz. The frequency is calculated by (P * Xtal) / (M << S).
Example 500MHz: ((125<<16)|(3<<8)|(0x1)), the format is ((P<<16)|(M<<8)|(S)).
(P * Xtal) = 125*24 MHz = 3000MHz
(M << S) = 3 << 1 = 6
End result is 3000MHz / 6 = 500MHz.
That's all you need to know. Alternatively, just copy what other devs have already done. Be careful with the Lx levels when you add new ones, you need shift all the existing ones throughout the file.
Click to expand...
Click to collapse
I'm a bit confused by what M << S means. From lookig at the example it looks like the formula is: P * 24 / ( M * 2^s)? Also, I'm assuming the voltage tables don't have to be touched. Thanks so much for the information. And... what fun would it be if you did a straight up copy and paste? :cyclops:

Ummm that's a bit-wise left-shift operation. And yes you also need to add entries in the voltage table.

AndreiLux said:
Be careful with the Lx levels when you add new ones, you need shift all the existing ones throughout the file.
Click to expand...
Click to collapse
And in any other files that reference levels... Namely any that contains a level-based DVFS lock.
I think much of Samsung's newer code does frequency-based locks with a frequency-to-level lookup, but in older 4210 kernels, there were lots of locks that called out specific levels. Some of these locks were in throttling code. Levels go from high freq to low freq.
So if L2 was originally 800 MHz, and L2 is now 1000 MHz, and thermal throttling code locks to a minimum level (maximum frequency) of L2... Whoops, now the thermal throttling is broken.

Hi again,
For some reason, the exynos4 sources seem to be much more fussy than the galaxy tab 10.1 tegra2 sources I messed with in the summer. Right of the bat (with no modifications), it refuses to compile giving me issues in the file arch/arm/mvp/mvpkm/mvpkm_main.o. I haven't touched anything or made any changes yet. I downlaoded the latest sources from Samsung. I tried switching toolchains and I get 1 of 2 errors. With an older toolchain I get
/tmp/ccC3yZT8.s:4865: Error: unknown pseudo-op: `.arch_extension'.
With a newer toolchain I get an error about making a pointer to int conversion without a cast. Wow, truly unbelievable!!!??? I just want to make a baseline run, haven't touched a character of code and it refuses. I tried compiling CM10.1's kernel (also with no modifications) but for some reasons the graphics are Pentium 1 slow. ADB shell with logcat keeps saying hwcompser can't do vsync and it attempts to fake it.
I don't remember it being this hard on my galaxy tab 10.1. Am I missing something obvious?
---------------------added-----------------
I got cm sources compiling correctly. I think i forgot to undo previous experiments

AndreiLux said:
Each divider value represents the real divider minus 1. So a value of 7 divides by 8. Populate the divider talbes with new entries like that. The registers have a limit so see the register maps in /mach/regs-clock.h. The dividers divide the final CPU clock. What values you give the dividers is up to you to decide.
The CPU clock is decided by the PLL as you saw. PMS decides the PLL frequency. The source quartz runs at 24MHz. The frequency is calculated by (P * Xtal) / (M << S).
Example 500MHz: ((125<<16)|(3<<8)|(0x1)), the format is ((P<<16)|(M<<8)|(S)).
(P * Xtal) = 125*24 MHz = 3000MHz
(M << S) = 3 << 1 = 6
End result is 3000MHz / 6 = 500MHz.
That's all you need to know. Alternatively, just copy what other devs have already done. Be careful with the Lx levels when you add new ones, you need shift all the existing ones throughout the file.
Click to expand...
Click to collapse
I have been meaning to thank you for this, I have not seen this information elsewhere. Could you please briefly explain how to set the values in cpufreq_clkdiv? I have noticed different kernels have different values for the same frequency, and I don't know which one is correct for me.
Example:
/*
* Clock divider value for following
* { DIVCORE, DIVCOREM0, DIVCOREM1, DIVPERIPH,
* DIVATB, DIVPCLK_DBG, DIVAPLL, DIVCORE2 }
*/
Samsung source (I believe)
/* ARM L0: 1600Mhz */
{ 0, 3, 7, 0, 6, 1, 2, 0 },
Perseus:
/* ARM L0: 1600Mhz */
{ 0, 4, 7, 0, 6, 1, 7, 0 },​

ffolkes said:
I have been meaning to thank you for this, I have not seen this information elsewhere. Could you please briefly explain how to set the values in cpufreq_clkdiv? I have noticed different kernels have different values for the same frequency, and I don't know which one is correct for me.
Example:
/*
* Clock divider value for following
* { DIVCORE, DIVCOREM0, DIVCOREM1, DIVPERIPH,
* DIVATB, DIVPCLK_DBG, DIVAPLL, DIVCORE2 }
*/
Samsung source (I believe)
/* ARM L0: 1600Mhz */
{ 0, 3, 7, 0, 6, 1, 2, 0 },
Perseus:
/* ARM L0: 1600Mhz */
{ 0, 4, 7, 0, 6, 1, 7, 0 },​
Click to expand...
Click to collapse
I don't have any exact technical explanation behind the physical CPU blocks that those auxiliary dividers are clocking.
Personally I just fired up Excel and adjusted them in to what seemed to me a reasonable curve with the rest of the frequency clocks which Samsung provided. These are the values I put in Perseus.
{
"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"
}
You could probably adjust M0 again beyond 1800 MHz to be somewhat lower.