- Nougat version: this post -
BLX
Moxie provides Battery Longevity eXtension, a feature that I believe is currently unique to this project. BLX prevents your battery from charging to its full capacity. Why is this useful? Because charging your battery reduces its capacity over time. To help prevent this, I've designed this mod to cut off the battery charging earlier. (Testing of BLX: this post and rationalle: this page)
To enable BLX edit:
/sys/class/misc/batterylifeextender/charging_cap_level
Click to expand...
Click to collapse
to any value from zero (disabled) to 10 (full BLX). I've found that when using the DASH charger, 10 works well and limits the charging to about 80%. For non-OEM chargers, a value of 5 has the same effect.
Still using Marshmallow? (I am!)
Final M kernel: This Post
Coming from another custom (Marshmallow) kernel? Check this link!
Remember to hit thanks for NevaX1
{
"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"
}
* * *
In order to comply with GPL, linux kernels may be modified and distributed so long as their source code and compilation tools are public, allowing anyone to reproduce an identical binary.
Toolchain: here
Kernel Source: https://github.com/bedalus/oneplus3kernel
Wifi Module Source: https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0
I accidentally vented a post on my development philosophy: here just in case anyone is interested in how I approach development!
I realise this isn't very exciting (yet) but I'm posting here to keep a public log of this kernel development from scratch.
About me: I developed for the Nexus S ages ago! Left XDA but have since returned, hoping to keep things more low key.
Github commits
Commit fb944f9:
I just want to go over the build script a little for anyone who might like a little insight into the development process.
Code:
echo -e "Making OnePlus 3 kernel\n"
export PATH=$PATH:/opt/toolchain/lin531/bin/
export ARCH=arm64
export SUBARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu-
make msm-perf_defconfig
make -j5
# modules
find ./ -type f -name '*.ko' -exec cp -f {} ../zip/system/lib/modules/ \;
# copy zImage
cp -f arch/arm64/boot/Image.gz-dtb ../zip/kernel/zImage
ls -l ../zip/kernel/zImage
cd ../zip
zip -r -9 op3_vN.zip * > /dev/null
mv op3_vN.zip /mnt/c/Users/bedal/Downloads/
I've got my cross compiler located at /opt/toolchain which I believe is pretty standard. The cross compiler is Linaro, although there are many other choices available. I've selected Linaro because they are a large professional organisation, and contribute a lot to development on ARM architectures. ARCH is short for Architecture, as you can see in the top lines. The export command just passes the target architecture to the compiler, so we can build binaries that will execute on ARM chips.
It's also worth noting that we are cross compiling since we are developing on a different platform to our target. In fact I'm using bash for Windows on a 64 bit Lenovo laptop! This is an AMD64 architecture, which used to be commonly known as x86_64.
Code:
make -j5
This sets the build off, then
Code:
find ./ -type f -name '*.ko' -exec cp -f {} ../zip/system/lib/modules/ \;
...is just a handy bit of code to find any modules and move them to the necessary spot in my 'zip' subfolder. As it happens I'm building only the WiFi module, as the wifi code appears to have a problem running when built into the kernel binary.
The rest of the code is fairly trivial. The zip file that you flash in Recovery is just the new kernel binary, plus the wifi module, plus a script that extracts your existing ramdisk from your ROM's boot partition, discarding the old kernel binary in favour of the new one, before re-integrating and flashing back to the boot partition. I may go into that in more detail in a later post.
Commit e5403fd:
I want to just briefly mention the file: sound/soc/codecs/tfa9890/tfa_container.c
In order to better ensure that the kernel works correctly, the compiler will report anything it sees as an error and stop compiling. When I first tried to build the kernel, one of the first errors I got was with this file. The warning the compiler gave me was something like 'in procedure blah-blah, an if statement will always evaluate to TRUE'. So why is this a problem? Because clearly the developer used an if statement so that a choice could be made. If the condition specified in the if statement evaluates to TRUE, do one thing, if not (ie FALSE) then do some other thing. So the compiler suggests caution, because clearly an if statement can only pick the first option if the condition is always going to be TRUE.
Code:
[COLOR="Red"]if (!prof->list[i].type == dscRegister) {[/COLOR]
[COLOR="SeaGreen"]if (prof->list[i].type == dscRegister) {[/COLOR]
My solution (above) shows the line that was removed in red, and the replacement in green, and it should be pretty obvious that the exclamation mark was removed, and no other changes were made.
The reason that I bring up this specific change is that I've seen other solutions to this problem in other dev's source code, and while they may trick the compiler into believing the problem is solved, really the problem is worse. Generally speaking, it is in fact possible, indeed probable that code will make it through the compiler just fine, even though when executed it will cause a fatal error (an error that cannot be recovered from, ie a crash). So what's up with this code?
The exclamation mark is shorthand in C for 'NOT'. NOT reverses a boolean value, ie Y becomes N, N would become Y, and TRUE -> FALSE and of course FALSE -> TRUE!
We can see in the code that it appears to be trying to invert the logic of a list type. Let's pretend it's a shopping list. So what would 'NOT shopping list' be? One thing that's not a shopping list? Or all the things that aren't shopping lists? It's a nonsensical proposition, and I think some developers have looked at the code and thought, 'huh, that's in the wrong place,' and have fixed it by taking it out of the brackets.
Code:
if !(prof->list[i].type == dscRegister) {
If you remember your high-school maths, the contents of brackets are always evaluated first. The fixed (wrongly) code now tests if one list type now matches another. That's fine, if it's a match then we get TRUE. If not then FALSE. Now we know if whether it's one or the other, the '!' will flip it. Then the if statement will progress to the next bit of code, doing whichever thing is required based on the outcome of the test.
That's all well and good. The compiler can see this and compile it without throwing an error. The problem is that the '!' shouldn't be there at all. If this wrong-code is ever executed, because the '!' has flipped the logic, the wrong path will be taken.
Any other devs who are reading this and know this may be the method they used to fix the compiler warning should take a good look at the code in that one file. It should be obvious that the '!' shouldn't have been there at all, and was probably a typo at the original development stage that wasn't picked up by their compiler (older compilers couldn't spot as many different kinds of problem).
Any discussion will be most welcome. This is the sort of thing I feel should be going on at XDA but seems to be conspicuously lacking in the development forums!
Good to see another dev Greetings brother!
Welcome to the party @bedalus!
Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
@bedalus Tnx a lot for this!!!!
Thanks Keep up the Work !
Wow.. Glad to have you here bedalus back from nexus s days
Sent from my ONEPLUS A3000
First and foremost, thank you for sharing post 2. That kind of stuff is why I really come here. With that said, I flashed your kernel and it lives up to the name. The kernel is fast and fluid with all my tasks. Thanks for sharing your work and development skills with us :good:
mixtapes08 said:
Wow.. Glad to have you here bedalus back from nexus s days
Click to expand...
Click to collapse
Hey mixtapes, it's a small world! I'm a better programmer than I was back then. Well, maybe not better, just more patient
How've you been? What phones have you rocked since the Nexus S?
AlkaliV2 said:
First and foremost, thank you for sharing post 2. That kind of stuff is why I really come here. With that said, I flashed your kernel and it lives up to the name. The kernel is fast and fluid with all my tasks. Thanks for sharing your work and development skills with us :good:
Click to expand...
Click to collapse
I enjoyed writing it and I'll try to keep it up. I want to provide more insight into what each update has actually changed.
Oh that's good to hear. . Nexus 4,5,6p then op3. 4 and 5 are both sold already 6p on my girlfriend and I have op3 and the oldest nexus s that I use for alarm lol. How about you?
Oops I forgot the galaxy nexus that also sold already hehe.
Sent from my ONEPLUS A3000
mixtapes08 said:
Oh that's good to hear. . Nexus 4,5,6p then op3. 4 and 5 are both sold already 6p on my girlfriend and I have op3 and the oldest nexus s that I use for alarm lol. How about you?
Oops I forgot the galaxy nexus that also sold already hehe.
Click to expand...
Click to collapse
Yep, Nexus 4. I think I saw you over in that forum too IIRC. Then I got sick of it all, and rocked a dumb flip phone for a while. I thought I was in the matrix. Then I got a HTC One X plus, but it was too heavy, and I really didn't think the beats audio was that impressive. In fact I thought it sounded bad. Incidentally, I think the audio from the jack in the op3 sounds very good!
I later had a go with a Nokia 830, which was an excellent device, but as everyone says, Windows Mobile is a poor ecosystem. The OS itself was a bit ropey too.
I also had a Moto G 2nd gen at some point. Another solid device, but a bit too discrete for my taste! I then had a Sony X3 compact. A very nice device! But I broke the screen
I'm sure I'm forgetting some. But I felt the op3 was a total bargain at the price. I couldn't resist. It's a bit short on battery, but that's my only gripe.
Okay, it's been hard work, but v2 is here: http://d-h.st/qUqT
I'll go into detail about the commits in the next day or two.
Delete
Gesendet von meinem ONEPLUS A3003
@bedalus
What is up with this thread theres no OP (1st post). no info at all
what is this kernel for OOS, CM, AOSP?
I am no dev and am probably asking a silly question. But could one compile the current cm14 N kernel with this and build a custom N kernel?
Sent from my ONEPLUS A3000 using Tapatalk
partridge79 said:
@bedalus
What is up with this thread theres no OP (1st post). no info at all
what is this kernel for OOS, CM, AOSP?
Click to expand...
Click to collapse
It says it's for stock on the OP, meaning OOS. Also if you click the GitHub link you'll see it's forked from the official stock OOS kernel source, as well as in the repo you'll see the branch is called stock.
So if I had to guess I'd say it's for stock ROM..
@jukiewalsh
I was using xdalabs and there was no OP at all the 1st page had 1 post from a moderator saying thread cleaned (hence my post saying theres NO OP. So no links to click either but coming back now i see that OP has been restored along with the rest of page 1. (Which has all the info i required) Must have been some maintenence being done to post thanks for the heads up tho
partridge79 said:
@jukiewalsh
I was using xdalabs and there was no OP at all the 1st page had 1 post from a moderator saying thread cleaned (hence my post saying theres NO OP. So no links to click either but coming back now i see that OP has been restored along with the rest of page 1. (Which has all the info i required) Must have been some maintenence being done to post thanks for the heads up tho
Click to expand...
Click to collapse
Ohh okay haha gotcha
Will this work with community builds?
Sorry if it's a stupid question..
---------- Post added at 05:52 PM ---------- Previous post was at 05:35 PM ----------
dpryor88 said:
Will this work with community builds?
Sorry if it's a stupid question..
Click to expand...
Click to collapse
Edit:
It doesn't. Haha.
Related
All Credits to snq- Desire Dev......thanks man!
Finally!! Yes We Can!!
http://forum.xda-developers.com/showpost.php?p=9489090&postcount=81
rikwebb said:
m-deejay fix posted
http://forum.xda-developers.com/showpost.php?p=9492320&postcount=3010
Click to expand...
Click to collapse
snq- said:
new sense + htc camera app on a desire classic:
just made a few shots, camera seems to be fully functional, tested also w/ quickmark
there is still an issue w/ the camcorder, i'll try to fix it and release rsn
Click to expand...
Click to collapse
snq- said:
due to popular demand and due to the fact that i can't work on this in the next few days i'm releasing this update as is for robocik's rcmixhd v0.12
camfix_rc1_rcmixhd012.zip
works:
camera (also with 3rd party apps like goggles, quickmark or cam360)
camcorder (w/audio)
yet to fix:
720p (do NOT set hd resolutions in camcorder mode)
some aftereffects in camera mode
Click to expand...
Click to collapse
Giblet-dono said:
Hey Guys!
Stumbled upon this thread and the fix,
im using Phiremod ACE Sense HD build
The way to push this fix to your device is as follows:
Insert SDcard in computer (through mobile or cardreader)
In the camfix file youll find 3 folders (you can download in the first post)
Ignore meta-inf
Copy the file HTCCamerpa.apk from sd-ext/app_s to your sdcard in the folder:
sdcard/android/root/system/apps
If the folder does not exicst, creat it!
Then copy the contents of the system folder (all of them) to Sdcard/android/root/system
After this reboot your device
WARNING! You are doing this at your own risk!
This "fix" creates graphic glitches on the screen!
Make a BACKUP!!
Camera DOES work
Camcorder DOESN'T WORK!
Goodluck!
Click to expand...
Click to collapse
Some HD2 user reports;
netdrg said:
Tested and work on HD2
{
"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"
}
Click to expand...
Click to collapse
netdrg said:
I Create my proper build not push or update files
Click to expand...
Click to collapse
Click to expand...
Click to collapse
dharvey4651 said:
Just tested the files using the root folder method and it DOES seem to work very well on the HD2.
I'm using it on mdeejay's Froyo HD 3.7. I'm able to take pictures with a working flash(no green tint). The only downside I'm seeing is that it creates a glitchy affect where horizontal lines appear randomly(but consistently) on different parts of the screen unless there is motion on the screen.
I'm going to modify mdeejay's build and cook the files into the build and test from a clean install and report back if the glitch is still present afterwards.
Click to expand...
Click to collapse
_____________________________________________________________________________________________________
Hi, people and Devs, some Desire Devs are working hard in camera port to HD and Z Rom.....and they solve the camera issue, We are in, too.
20\10 - Today they was able to run a camera on HD Rom!
I have much hope in their work, and maybe our Devs can give a hand to Desire Devs, to solve this issue......We are all XDA bro.
We can see, the development thread, here:
http://forum.xda-developers.com/showthread.php?t=805159
And, we can regard the Desire Devs, here:
http://forum.xda-developers.com/showthread.php?t=814188
#1 - First Camera Working Test
20.10.10 - 02.03PM
http://forum.xda-developers.com/showpost.php?p=8722858&postcount=293
BlueVD said:
Here's a quick vid of the camera working... Sorry for the quality, I've done it using a laptop cam and it was enoying trying to adjust the lid at the propper angle...
You can see the Personalize menu at the start (just to proove it's SenseHD) and the skin is metallic
the console command was awb_camera
Click to expand...
Click to collapse
#2 - Release should come soon to Desire
20.10.10 - 10.43PM
http://forum.xda-developers.com/showpost.php?p=8731927&postcount=315
BlueVD said:
Well, first of all, I've already released the libs and binaries in a previous post (the one with the screenshot, not the video). Right now I'm working on the framework. And it is GPL since most of the things I've done is to recompile allready published source code. What I did modify are some files needed to build the Androis Os (taken from nexus one and adapted for the bravo board), not the kernel and I'll publish them soon. Just so that you know, I'm not keeping anything under "wraps". All the work I've done so far is with the help of google, readme files and comments on xda. Guess than in short it's something in the borderlines of RTFM. The framework is the toughest sob but with the subtle hint from ownhere I'm making some advances here also. I don't want to give false hope, but a release should come soon. It's moving slowly because of my job and the sleep depravation not to mention my old laptop running a dozen tasks and a VM.
Keep you posted on my progress.
PS: video recording might not be able to record sound in the first release (since there's somewhat of a rush to get the photo capabilities). The audio part of the framework will take some serious modding.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Click to expand...
Click to collapse
#3 - Status Update
BlueVD said:
Ok folks, another status update: had 3 frameworks so far, 2 fc'd and one didn't do anything at all. Right now I'm having one of my servers reinstalled in order to compile android to produce a custom framework. This one will be compiled with all the required stuff in it so it should work. As to sound recording in the video, chances are we're getting it too! It will take a few more hours to get the framework compiled, but please bear with me.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
#4 - New update
BlueVD said:
..... It's the sourcecode for android and I'd have to be darn stupid to post it once again since google took care of that. People can get their source code from there. And as a refference, all mods were done on the nexus files that came with it since desire shares most of the hardware. Geez folks, if you would know a bit of programming you would know that. And since you don't know programming why the heck do you ask for them? Sorry if I sound harsh, but these past few days I barely got 2 hours of sleep per night and all I'm chewing at is the camera, even at work. Have patience, redoing the framework takes some time. Trust me when I say that I'm doing everything humanly possible to get the fix as soon as possible. And if any dev wants to get the files I moded, he can PM me.
And stop posting friggin comments that have nothing to do with devel stuff! Makes it hard for me and the other devs keep track of stuff.
PS: let me make this clear, the existing framework is compiled with different drivers so to say. And the only way to change that is to modify it. I'm compiling a new one to get all the right values for the cam part and patch the existing one since the framework for a nexus would be incompatible with the one needed by SenseHD. If it were as easy as fooling around with a hex editor I would have done it already. And keep in mind that this is my first clash ever with android code. Besides doing the work I also need to learn a lot of stuff on the go! These being said I hope I won't have to read any more mindless posts. And yeah, if any other dev wants to do this step in my place, do tell. I'd be more than happy to give you all I have (and that is sidenotes! Cause the code is already available online). This way I'd finally be able to take a good night sleep
Sent from my HTC Desire using XDA App
[EDIT]: there's no front camera on the Desire Hd/Z. But HTC added the code for one. All I can presume is that they have one with SenseUI2 but no news of that phone leaked yet. Though it would seem sloppy of HTC to make such a silly mistake
Ive jusr noticed that the user asking for the sourcecode was neophyte. Mate, all I did was copy the vision files that came with the official source of android, comment out some lines related to the colors of the trackball and pull the proprietary files out of my desire. That's how the libs got done. All of this know-how came from xda forums. Like I said, there's no special voodoo I'm doing. As for the files, I'll get them online if you think it helps (but it doesn't since they only help with the making of the libs and those are already done and working).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
BlueVD said:
Ok, here are the files needed to build the libs and the framework with the correct interrupts. Hope you guys will be happy with them (like I said before I just copied the whole nexus one files and named them/modified them to suit bravo).
http://wbss.ro/android/device_htc.tar.gz
Prerequisites:
1) A linux machine with a x64 distro (I recommend ubuntu 10.10, even if Canonical said it's not all that stable. Also Mandriva 64 bit should do. I run these 2 distros and both seem to work) OR a windows machine that has a case sensitive FS/Partition (I never herd of such a thing, so I recommend linux)
2) 6GB free space
3) a lot of time
Steps:
1) get the android source (see http://source.android.com/source/download.html )
2) download the file I provided above and extract it into ~/devices/htc (~ represents the root of the sourcecode folder for android)
3) just build the thing. (make -j2 TARGET_PRODUCT=htc_bravo)
At the end of the build you'll find the libs and whatever else you would require... Happy compiling time to you all.
Click to expand...
Click to collapse
BlueVD said:
Whatever work I finish and it doesn't FC, segfault or harm the phone in any way will end up in http://wbss.ro/android
So if anything pops up there, you can use it...
....
Click to expand...
Click to collapse
#5 - Big update!!
http://forum.xda-developers.com/showpost.php?p=8749645&postcount=346
BlueVD said:
OK people, I will keep my english plain:
WHEN a flashable zip will be ready I will say it in BOLD that you can flash it via recovery. Until then, NO, THERE IS NO FLASHABLE ZIP.
And I'm not yelling, just pointing out what should be obvious.
And now, a requst for someone that has a HTC Leo with gauner1986's HD Rom:
BACKUP the files you will replace first!!! Otherwise you'll have to extract them from your ROM to put them back!
Download the following file http://wbss.ro/android/Bravo_Sensehd_workingCameraLibsAndBinaries.zip and upload the *.so files (via ADB with the phone in recovery) to /system/lib
After that upload the rest of the files (the ones without extension) to /system/bin
Reboot the phone, open your favorite console and run as root (and landscape mode, that it keep the phone upright):
Code:
awb_camera
I need to know if it outputs some text (like camera calibration status, etc). If it does, you should see a camera viewport in the upper left corner of the display. If you don't, just swipe your finger across the display and you should see some flicker in the upper left corner. If it does, good news: owners of LEO will get the camera fix as soon as the Desire one gets it.
PS: I've got a seminar coming this weekend... Hopefully, I'll finish the fix by tomorrow evening, if not, it's up till monday
Click to expand...
Click to collapse
BlueVD said:
I talked to gauner1986 and his rom is based on the dump from DesireHD. I've specified that peole using his rom should test the libs But it's good to know that apparently something failed on Mdeejays rom. Hopefully it will work on gauner1986's rom.
Click to expand...
Click to collapse
#6 Someone did it!
http://forum.xda-developers.com/showthread.php?t=786316
a haha happy
pack21 said:
Hi, people and Devs, some Desire Devs are working hard in camera port to HD and Z Rom.
And today they was able to run a camera on HD Rom.
I have much hope in their work, and maybe our Devs can give some help in that.
http://forum.xda-developers.com/showthread.php?t=805159&page=31
Click to expand...
Click to collapse
Good news for sure! I guess we will have a fully functional desire HD rom running at our precious HD2s before the end of the weekend.
@BlueVD
many thanks for the info
paalkr said:
Good news for sure! I guess we will have a fully functional desire HD rom running at our precious HD2s before the end of the weekend.
Click to expand...
Click to collapse
i hope so too
Great news!
Sent from my HTC HD2 using XDA App
If this is true, that would be brilliant indeed
good news i wait it thanks
Great!!!
excellent!!
interesting!!
I find the HD rom most stable. It would be very good when camera can be used in this excellent rom. thanks so much!
good job ~~
Great news!
Really appreciate about the efforts of devs and chefs.
Looking forward to the good news.
Ambious said:
Click to expand...
Click to collapse
Me too..!!!
Well XDA Dev ROCKS..!!!
I think its a fake. I havent seen anything on irc about it
wow great news
Ambious said:
Click to expand...
Click to collapse
^ Lmao
Anyways what a giant leap for mankind, now i can continue sexting!
elgrego4 said:
I think its a fake. I havent seen anything on irc about it
Click to expand...
Click to collapse
You don't see in irc, because this is from Desire Development, but if they can port a camera on HD Rom, so our Devs can do the same......the difficult is to find a way to port the camera, in Desire or HD2 device.
We can pray and thanks for Desire Dev work in this issue.
I hope this means they can get the camera working on the G2 and myTouch HD roms too
you rock guys!
AMAZING !!!!!! hope we have a working camera !!! SOON...
Thanks devs !!!!
Right. So, on request from a few users below, I shall be giving a very broad description of what clickDot is, and I shall be updating this post with details over the next few days.
Let me just state before I begin: I am not looking for any testers at the moment, so please, don't waste your time asking to test this. In time, I shall pick a handful of people to help me test parts of the program. Let me also ask that you guys do not ask for a release date - not even I know the release date yet, and I cannot commit to anything. I am a university student, hence I also have other priorities to see to. When I can work and update you guys, I will. Also, for those wanting to know what will be required to run this UI, you may take a look in the FAQ section once I've posted it.
So, back to the description. What I found in my personal experience is that, especially with typical home launchers like LancherPro, ADW, the original Android Launcher or anything of the sorts, is that information can become cluttered. You often need a single widget to display a certain piece of information, and for those who like to have multiple bits of information shown to them simultaneously, find themselves with cluttered home screens that have no consistent theme or look.
Where clickDot differs from most UI's is that it only shows the cluttered information on demand (Pictures will follow to illustrate the idea). The initial home screen of clickDot will only contain a simple bit of information in the center of the screen, mainly about your current surroundings, such as:
Current weather (pictures and possibly animations)
Current date and time
Current temperature
Moon phase (shown during night time)
Missed emails, sms' and calls
More to follow...
Click to expand...
Click to collapse
All of the above will be shown in a relative manner, that being all fitting into a set theme and look.
If you click on the center of the weather image (Better description and images to follow), a drastic change in the UI will occur. Everything mentioned above will scale away (disappear, with the exception of a few bits of information, mainly being time and date) and a circular disc will appear. The disc will be broken into segments that will contain links to certain other applications and sections of Android. So far, the list of applications that will be developed and built into the UI, are:
Facebook
Twitter
Phone
Messages
Email
Click to expand...
Click to collapse
The idea of the disc is to give quick access to not only common applications, but information from these respective applications as well. If a segment is clicked, the disc is shrunk to a small circle with the icon of the selected program (hence the dot part of clickDot). The dot then moves to the bottom of the screen, and the respective application is displayed. Once again, images will eventually follow to make this easier to understand.
EDIT: I have not been able to finish a promo image of the launcher (time is really tight), but here are the weather images I have created so far. Some of them need work still, but this is what I have at the moment. During the day, the sun will always be displayed, and during the night, the moon will always be displayed (as the relevant phase). All other weather images will be layered on top to show the relevant weather. Here is the image:
{
"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,
MrP.
UPDATE (08/02/2011): Added weather promo picture
Reserved for FAQ
Any screenshots?
Sent from my GT-I9000 using Tapatalk
MrPadie said:
Details coming soon.
Click to expand...
Click to collapse
Well you've just created a thread to type "coming soon".
Just give us the basic things, then give the details later.
What is ClickDot ?
I like this thread. This guy is on the ball hes so ahead of the ball that the details are simply the details will be here soon. But on a seriously note it sounds interesting. I like the name.
"coming soon" threads are against the rules on xda, especially when they are lacking any details at all.
I would not be surprised if you find this thread locked soon.
Reserved for Quick Reply.
Unbelievable
Rootstonian said:
Unbelievable
Click to expand...
Click to collapse
Agreed!!!..
Thanks all for your 'kind comments'
The "coming soon" part of the thread was simply due to the fact that where I thought I had time to write up the post, I ended up being dragged off to other plans. That said, I shall have a meaningful post up in the next hour or two
I'm hoping you guys will enjoy it, and please, feel free to comment and provide input.
MrP.
EDIT: As requested, an initial post to briefly describe my idea. More detailed description to follow soon.
i am very intrigued to see what this has to offer, the name sounds cool
No offense, but i really wish developers would actually develop something before releasing info about it. It's getting very tiresome reading "coming soon!" threads. Most of the time the UI never actually gets completed.
Sounds like an interesting approach but I would need to be able to add sections and items to the DOT before I would be willing to adopt.
I pretty much try to organize my phone into the following categories.
Phone
Voicemail (I use Google Voice)
Email
Messaging
Location
Media
Internet
Social
App Launcher
Unfortunatly LP Pro only has 7 screens so I am up for a new UI that will allow me to do that.
Hope to see screens soon!
Although you do raise a good point, Meltus, which I've seen happen countless times, and although even me, as the developer cannot guarantee that this UI will be fully developed and released in good time, I have to point out one simple fact:
As a developer, I find constructive criticism and commentary on my work a blessing in disguise. If I incorporate the requests and criticism from the community as far as possible into my work, I will hence create a product that is attractive in the sense that it's close, if not exactly what the community wants. Developing the product first could mean a lot of work going back and redoing parts to overcome problems and/or highlight points that I have overlooked.
In my eyes, this is a community. No where in my thread title did I state that the UI has a guaranteed release, or a Beta available, or a release date already. It's simply a post describing my idea to allow the community a chance to input into it before I create a final product, which I would like to finally have.
On a side note, I think this "coming soon" story that was originally in my first post has gone too far. It's got nothing to do with the fact that I'm spamming or trying to build hype, it simply was due to the fact that I had to leave for uni earlier than expected, and could not finish what I was typing up. Hence, I posted "coming soon" instead, and when I got home after uni, updated the post with the finished details, which, isn't even complete yet. Just clearing that up.
@Asphyx - thanks for your input. I haven't given too much thought into the customizability yet of the circle/dot, but it is definitely on the to-do list. I feel the same as you - the user shouldn't adapt to the UI, but instead, the UI should adapt to the user. Let me see what ideas I can come up with, and I'll get back to you. So far, what I have in mind is that the circle/dot will be divided into 12 segments. I might have segments that cannot be changed and segments that can, or I might have them all editable. Where I do not have a separate application developed yet for, say, Media, it will launch the Android default. What I'm also planning on doing is creating a system where you can create as many home screens as need be that you can use to add widgets, and then create a link to these separate home screens in the circle/dot. For example, if you have widgets that you use to view Media information, you can create a panel that is called Media. You can add and edit the widgets on this panel, and you can access it by clicking a corresponding link in the circle/dot. That might appeal to those still wanting to use widgets.
MrP.
MrPadie said:
Although you do raise a good point, Meltus, which I've seen happen countless times, and although even me, as the developer cannot guarantee that this UI will be fully developed and released in good time, I have to point out one simple fact:
As a developer, I find constructive criticism and commentary on my work a blessing in disguise. If I incorporate the requests and criticism from the community as far as possible into my work, I will hence create a product that is attractive in the sense that it's close, if not exactly what the community wants. Developing the product first could mean a lot of work going back and redoing parts to overcome problems and/or highlight points that I have overlooked.
In my eyes, this is a community. No where in my thread title did I state that the UI has a guaranteed release, or a Beta available, or a release date already. It's simply a post describing my idea to allow the community a chance to input into it before I create a final product, which I would like to finally have.
On a side note, I think this "coming soon" story that was originally in my first post has gone too far. It's got nothing to do with the fact that I'm spamming or trying to build hype, it simply was due to the fact that I had to leave for uni earlier than expected, and could not finish what I was typing up. Hence, I posted "coming soon" instead, and when I got home after uni, updated the post with the finished details, which, isn't even complete yet. Just clearing that up.
MrP.
Click to expand...
Click to collapse
Sorry, i didn't mean to question your ability or commitment to the project, i'm very aware that some projects just fall by the wayside every now and then and never get completed, which is no fault of anyone.
I fully agree with having community input, i just meant that maybe a photoshp "mock-up" or screenshot would help move things along tenfold.
That way the community can see what the final product may look like and can offer constructive criticism. Getting the code down is all well and good, but the aethestics are what makes a good UI amazing.
Writing what your app will include can be done by anyone (again, i'm not questioning your ability) but showing how these features will be implemented will get a lot of people interested.
@Meltus - Duly noted. Being a uni student, time is often not on my side, but I shall whip up something and hopefully have it up by tonight.
Thanks again for the input,
MrP.
I am really waiting for this!! Looking forward to see it soon!
I think if someone's screen is "all cluttered-up" it's their own fault. My Droid X has the home page and 3 screens to the left and 3 screens to the right. I'm assuming most Android devices are somewhat similar. If you've got those ALL filled, I would love to see some screen shots LOL. Only thing I don't like is not being able to set the icon spacing; I can only get 4 icons in a vertical column, it has room for 7.
Granted, this UI is intriguing and may prove interesting. It might be cool to have a UI with just ONE screen...this "dot" idea. I can see it as some type of "fanned" menu or a wheel you can spin to get to items. Like if you long press "Media" the wheel (or dot") can open up "News, My RSS feeds" etc.
Like platters of a disk drive..you see one "flat" wheel, but 20 more are underneath. Especially if you can "flick" the top "wheel", it folds in 1/2 and you see the wheel underneath and can spin it and so on for remaining wheels. Like a stack of CD's you buy...you can have hundreds of virtual wheels
This could get interesting.
Thanks Rootstonian for your comment.
I think you've described it the best so far - trying to incorporate as much of the UI into one screen as possible, and constantly change it according to what you're viewing.
To be honest, I didn't imply anything about multiple disc layers, but now that you've brought it up, I quite like the idea. I shall see what I can do about incorporating it into my design. It could really prove useful, especially for things like common settings (on/off switches).
Shall work on this and get back to you guys.
MrP.
MrPadie said:
@Meltus - Duly noted. Being a uni student, time is often not on my side, but I shall whip up something and hopefully have it up by tonight.
Thanks again for the input,
MrP.
Click to expand...
Click to collapse
Haha, i know how that feels!
Looking forward to seeing it!
Hey, i post it on deviantART a mockup of a music player for android that i made some time ago. Some people give me suggestion of posting it here, maybe anyone wants to make something with this.
P.S.I'm not being able to post image here, check it at m DeviantART page
thiago-silva.deviantart.com
I can make PSD available (it's free, no worry ;-)) if anyone wants.
Share your thoughs, if anything is missing, if something should be changed...
Any other stuff, just contact me.
And here is the screen:
{
"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 think it's very nice, and worth a go. Any dev?
common XDA!
I would be VERY interested in seeing this developed... If only I could code Java.
If we make it an open source thing I'd be happy to contribute some code from BlueMuze
https://market.android.com/details?id=com.alostpacket.bluemuze
I don't know anything about running an open source project though so. But I have some mediaplayer and album art utils I could probably contribute.
Design is uber too btw
I am interested in helping to implement it under MVVM with Android Binding
andytsui said:
I am interested in helping to implement it under MVVM with Android Binding
Click to expand...
Click to collapse
No offense meant by this at all, but can you explain why this would be helpful?
From what I gather MVVM is a new design pattern created to solve coding problems with Windows Presentation Foundation. This is hardly a time tested classic like MVC. It seems like shoehorning an MS technique into java (square peg, round hole). It also doesn't look complete... v0.2?
It seems to me, that if we're going to make this an open source project, we should pick design patterns that people know, and that fit the job. I'm not convinced a framework is needed at all too, especially with a media player on a limited power/resources device. Inverting control to a framework can (potentially) be limiting in where you can make optimizations and adds another layer to the stack.
Your framework looks like a very nice start though, and it looks like it will be very helpful for WPF/Silverlight coders making the move to Android some day. But from what I can understand of it at a glance, I'd wouldn't recommend it for this project unless all the coders were former WPF devs and you were further along in finishing it.
Android also already has a fair amount of code built into the API for binding adapters to views too. And where we bind will be cruicial for perfomance. Remember, music collections are often 1000 songs or more, and the data is in multiple tables. Cursor adapters also don't always work well because you dont want to be doing a DB lookup at every turn, while also decoding album art (skia with throw a bunch of OOM errors). We need to be very careful to reuse views and not maintain references to dead objects. (Something a framework can sometimes do unbeknownst to the programmer).
Unless... I don't know....maybe I'm completely misunderstanding what you're saying. If I am I appologize.
Anyways I'm still happy to donate my database utils and album art utils, (neither of which are perfect either) but what this project really needs is a lead willing to begin setting up the repo, and willing to devote time to integrating patches / setting standards.
My friend and I have done some dev work on games and minecraft things before for fun, maybe this could be something real we could have a go at.
Sent from my SCH-I500 using Tapatalk
alostpacket said:
No offense meant by this at all, but can you explain why this would be helpful?
From what I gather MVVM is a new design pattern created to solve coding problems with Windows Presentation Foundation. This is hardly a time tested classic like MVC. It seems like shoehorning an MS technique into java (square peg, round hole). It also doesn't look complete... v0.2?
It seems to me, that if we're going to make this an open source project, we should pick design patterns that people know, and that fit the job. I'm not convinced a framework is needed at all too, especially with a media player on a limited power/resources device. Inverting control to a framework can (potentially) be limiting in where you can make optimizations and adds another layer to the stack.
Your framework looks like a very nice start though, and it looks like it will be very helpful for WPF/Silverlight coders making the move to Android some day. But from what I can understand of it at a glance, I'd wouldn't recommend it for this project unless all the coders were former WPF devs and you were further along in finishing it.
Android also already has a fair amount of code built into the API for binding adapters to views too. And where we bind will be cruicial for perfomance. Remember, music collections are often 1000 songs or more, and the data is in multiple tables. Cursor adapters also don't always work well because you dont want to be doing a DB lookup at every turn, while also decoding album art (skia with throw a bunch of OOM errors). We need to be very careful to reuse views and not maintain references to dead objects. (Something a framework can sometimes do unbeknownst to the programmer).
Unless... I don't know....maybe I'm completely misunderstanding what you're saying. If I am I appologize.
Anyways I'm still happy to donate my database utils and album art utils, (neither of which are perfect either) but what this project really needs is a lead willing to begin setting up the repo, and willing to devote time to integrating patches / setting standards.
Click to expand...
Click to collapse
Man, I agree most of what you say.
Talking about the pattern itself is not the scope of this thread, so I should keep it short. MVVM is a derivative from MVC, while MVC is, as you suggested, a long-tested pattern, it doesn't really fits well in windows-based UI and that's why MVVM is suggested. No matter MVVM, MVC, MVP are all about clean separation of responsibility, to me, Android Activities are too overloaded. I like programming Android stuff, but at the very first I started it feels so 1990s in terms of UI. That's the reason I started the framework. (well, XML layout is at least better than SWING)
-------------------------------
Back to the project, I agree a project lead is needed, I think I have quite some spare time to take this post, only my time zone (GST+8) might not easy for interactive discussion.
I wouldn't worry to much about the timezone thing. This seems like the kind of project that could take a considerable amount of time to finish. So might as well take it slow and we can use message boards & emails to communicate.
Hopefully a few more devs will pitch in too.
alostpacket said:
I wouldn't worry to much about the timezone thing. This seems like the kind of project that could take a considerable amount of time to finish. So might as well take it slow and we can use message boards & emails to communicate.
Hopefully a few more devs will pitch in too.
Click to expand...
Click to collapse
Fine. So far we have:
Initial design (thiago-silva)
DB and Album Art caching (alotspacket)
UI (by me)
For me the major part that don't know how to do is the equalizer since it involves lots of signal processing and (maybe) ndk work, moreover, the UI designer didn't yet jump in to say anything?
Yeah EQ is the hardest part, it would have to be done in the NDK if we're planning on supporting anything older than Gingerbread. In Gingerbread I think we could use some of the newer audio features but I'm not 100% sure.
Agreed also that I would love to hear from the original poster, forgot to check how old this thread is, since it was bumped recently... Looks like it was a bit over 3 weeks ago.
I sent him an email (through the forum) so hopefully he will drop by
Hey, it's me here
Love the idea for a open-source project, if you guys need some help i'll be glad to provide it.
alostpacket said:
Yeah EQ is the hardest part, it would have to be done in the NDK if we're planning on supporting anything older than Gingerbread. In Gingerbread I think we could use some of the newer audio features but I'm not 100% sure.
Click to expand...
Click to collapse
I didn't take much time to look at Gingerbread or Honeycomb SDK yet, but no matter what, I think supports to 2.1+ will be the best (2.3+ is too niche at the moment) so we need some NDK eq coder... or just leave that in future update.
thiago-silva said:
Hey, it's me here
Love the idea for a open-source project, if you guys need some help i'll be glad to provide it.
Click to expand...
Click to collapse
If we got enough man-power, a more detailed story board might be needed.
Try contacting @eliotstocker for help. He made Music Mod. It was a great music player, but for some reason he stopped working on it.
I would love to offer some coding assistance!
Sent from my PB99400 using XDA App
We should pick a license too. I would vote for Apache just because that would allow us to use code from the AOSP if need be (also very business friendly so any of us could take the project off in other directions if we desired)
seclm193 said:
I would love to offer some coding assistance!
Click to expand...
Click to collapse
Which part you are most interested?
---
Either MIT or Apache will be fine for me, what about other devs?
Moreover, you guys prefer svn or git?
I'm an SVN fan myself but have been meaning to learn git for years now -- I just never git around to it.
{
"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"
}
General Info
It "worked", but don't set your expectations high (read the rest of the bullet points)
No hardware accleration (we knew this already)
I couldn't get a data signal (no 2G/3G), though it did see my AT&T SIM
Preferences/Settings are slim so I couldn't mess with APN settings to try to get data to work
Wifi will now connect (fixed in Build 2)
Couldn't test much at all due to no data connections working
Power button functionality was erratic. This seems to be fixed in Build 2.
Keyboard was actually very smooth
The OS became smoother after a few reboots, scrolling through windows felt Android 1.6ish, instead of being Windows Mobile 6ish
It shows a LOT of promise
Boots in about 5 seconds, shuts down in 1 second
Pictures of build 3 running on my Nexus S can be found here: http://uberamd.com/post/22200022691/build-3-nexus-s-boot-to-gecko
Changelog
Code:
Build 3:
- Code base from 4-27-2012
- Some tweaks made to get wifi working better (got some pages to load around 4-23-2012)
- Wifi now connects AND loads pages. This means that you can finally utilize the web browser and bundled apps.
Build 2:
- I now made it so the ROM can be flashed via CWM just like any Android ROM
- Code base from 4-12-2012
- Now connects to wireless (pages still won't load, looking into it)
Build 1:
- Initial release
- Restore via CWM "Backup/Restore"
Directions
Ensure you have ClockworkMod on your Nexus S with a unlocked bootloader
Boot into Android
Copy b2g_nexuss_uberamd_signed.zip to your devices SD card
Boot into recovery
(optional) create a backup of your current setup
Flash the b2g ROM
Reboot
Boom, B2G awesomeness
I tested it, and it works. It is a fresh B2G build for the Nexus S
Latest Download - Click Here!
Please do not use any version earlier than 2012-04-13! The earlier version is NOT flashable via CWM (it is a CWM backup archive).
About
These CAN now be flashed like any other Android ROM. Be sure to do a backup within CWM. You can always restore the CWM backup.
This ROM is compiled from official b2g sources, with occasionally modifications sprinkled in by me. Credit goes to those main b2g devs who are making awesome headway here!
These will be built and uploaded daily using the latest sources. The goal of this is to allow people to test B2G without having to setup a Linux build environment as well as download multiple gigabytes of code, and mess with udev. ulimits, and more.
You can follow any updates I have on this thread as well as the boot to gecko section of my website.
Will this work on the ns4g?
Sent via Tapatalk using a Nexus S 4G powered by Kangs ICS
jralabate said:
Will this work on the ns4g?
Sent via Tapatalk using a Nexus S 4G powered by Kangs ICS
Click to expand...
Click to collapse
From what I understand, yes.
uberamd said:
From what I understand, yes.
Click to expand...
Click to collapse
when u upload a flashable zip ill give it a shot
I tried it on the ns4g and the wifi seems to be not working so im guessing that its only meant for regular ns? and it looks like its not connecting thru the 3g either so im guessing its not for the ns4g
t2noob said:
I tried it on the ns4g and the wifi seems to be not working so im guessing that its only meant for regular ns? and it looks like its not connecting thru the 3g either so im guessing its not for the ns4g
Click to expand...
Click to collapse
In my OP I state that 3G and Wifi also didn't work on the GSM Nexus S. Could be an issue with the current code base. I'm going to do a full rebuild tomorrow and see if it improves.
uberamd said:
In my OP I state that 3G and Wifi also didn't work on the GSM Nexus S. Could be an issue with the current code base. I'm going to do a full rebuild tomorrow and see if it improves.
Click to expand...
Click to collapse
I should have read the whole post i just read certain things lol
MY BAD....
t2noob said:
I should have read the whole post i just read certain things lol
MY BAD....
Click to expand...
Click to collapse
No worries Hopefully we'll have more functionality in tomorrows build.
uberamd said:
In my OP I state that 3G and Wifi also didn't work on the GSM Nexus S. Could be an issue with the current code base. I'm going to do a full rebuild tomorrow and see if it improves.
Click to expand...
Click to collapse
to add on, the reboot is insanely fast, and i really mean it. shutdown is instant. NOT even almost. Yes instant.
I'm quite impressed of how Boot to Gecko developed since it was announced. Although it has no hw acceleration it performs pretty well when scrolling through wondows. I hope that it will be developed to become something big.
What bothers me is that it wants an internet connection for apps like Cut The Rope - does that mean that it will need a permanent internet connection?
Edit: I tested it for half an hour and it only ate up only 8% of my battery.. wow.
kostastoupas said:
I'm quite impressed of how Boot to Gecko developed since it was announced. Although it has no hw acceleration it performs pretty well when scrolling through wondows. I hope that it will be developed to become something big.
What bothers me is that it wants an internet connection for apps like Cut The Rope - does that mean that it will need a permanent internet connection?
Edit: I tested it for half an hour and it only ate up only 8% of my battery.. wow.
Click to expand...
Click to collapse
I believe it takes/will-take advantage of HTML caching to store applications offline after they are used once.
And yeah for having no HW acceleration, thus using a lot of CPU, it really was light on the battery. I'll see if the build today fixes anything, it'll be up this afternoon.
uberamd said:
I believe it takes/will-take advantage of HTML caching to store applications offline after they are used once.
And yeah for having no HW acceleration, thus using a lot of CPU, it really was light on the battery. I'll see if the build today fixes anything, it'll be up this afternoon.
Click to expand...
Click to collapse
I think we need a new sub forum .
Nexus S B2G development
Nexus S4G B2G development
Waiting for improved results. Great work buddy .
Sent from my Nexus S
That's really good and interesting! calls and sms working, no lucky with wifi
Thanks for this build
Subscribing , great work!
Sent from my Crespo4g using xda premium
I'll test the build this afternoon on my ns4g. hopefully we'll have data working. this is totally necessary for me. great work so far, btw!! I was wondering if we'd be seeing another b2g soon after the last thread was closed for stolen code.
Flashed it just now on my i9023. ignoring the bugs stated in the OP, all I can say is wow!
Even though it doesn't have HW acceleration, it runs pretty well...and almost instant on and INSTANT off...that's awesome!
Wasn't able to make calls or sms, but that'll be fixed at some point.
Really nice! When it's fully completed, I might even consider migrating
Subscribed and downloading. Let's see what happens .
Sent from my Nexus S 4G using XDA App
I tried it just now, and I must say it runs decently. It's exactly what I would expect on such an early stage.
I also found out you can access those pages it uses on your regular browser (homescreen.gaiamobile.org, sms.gaiamobile.org for example).
Also, if you long-press home you will get a 'recents' menu.
I'm assuming my i9023 wasn't able to get any signal because the baseband list didn't include the one for ICS.
Maybe you could add it in the next build? it's I9023XXKI1
skaboy89 said:
That's really good and interesting! calls and sms working, no lucky with wifi
Thanks for this build
Click to expand...
Click to collapse
How did you get calls and texts to work. I tried with no prevail on my ns4g.
This is amazing! its crazy how fast it boots and turns off!! If only data worked! It would be amazing!
Sent from my Nexus S 4G using XDA App
Preeminently, I have always wanted to contribute to the Eris community. This is my first rom, although don't assume I'm adept at this specific criteria. It is based off CyanogenMod, without it this would have never happened. From what I recall, there was a thread that stated a rom should be made for the Eris as music player.
Hence I felt I should contribute since I had leisure time. So I removed all the applications that would intrude to make the Eris a pure mp3 player.
I bring to you the Abridged Rom.
I removed vexing signal bars in the status bar.
It is ICS themed.
Holo launcher, which is surreal to the ICS launcher.
Holo locker, it is relevant to Jelly Bean lock screen.
Battery script by Decad3nce = XDA. To activate, go to Terminal Emulator, type su for superuser permission; then type batt-cfg.
To make the launcher load smoother, press "Menu" then "Launcher Settings", go to "Desktop Settings" then tick "Wallpaper Scrolling" off.
If the Android lock screen intercedes with the Holo Locker application, got to Holo Locker then turn it "off" then "on".
Got the keyboard to work, just got to Settings>Language & Keyboard> Select Language> (choose) English (United States). That's if you prefer that language.
(Latest release, in the Beats column)
My Disclaimer:
To use this specific development, it is implored that you accept these terms and/or regulations.
"You" means the end user. By accepting this particular software, script, etc; you assess that it was established in a venerable infrastructure. Also, that "you" preeminently will not contemplate a contentious and/or irreverent, sordid manner; if "you" you are incongruous with the implicated engineering "you" will not perform or incite any behavior antecedently foretold. Furthermore, this engineering is not perfection but is ordain as to what is perceived from it. The founding Creator is not to be blamed for glitches, etcetera; though he ensues that he will be inure to anatomize and rectify any flaws as "you" enunciate them for him. Should "you" be admonished to use this attire with your discretion, due to the Creator or affiliates not being responsible to any errors concurring or that may reside.
Hitherto, "you" are now in accord and conclude with these terms and/or regulations.
(Basically saying I'm not responsible for your actions )
Hopefully, you enjoy it :highfive:
Initial Release:
Update:
Beats Rom
Initial Release:
Update 8/13/2012
Update 8/19/2012
Okay, for some peculiar and vague reason 2shared thrashed my links, they do not work. I have deleted those builds, I have no idea why. Though I have preserved some not all. (I feel ashamed). I will upload them in my Skydrive, thus never having to worry about anything being deleted or any obstructions.
Only this bottom one works
Update 11/19/2012: http://www.2shared.com/file/V-S7YChm/HTC-Eris-Beats9.html
Skydrive (Including remnants of my builds)
Update 6/10/2013: https://skydrive.live.com/redir?resid=C77A9B2B559BD0CD!105&authkey=!AHSqdyLCF9IGm4Y
From my "Copy.com" cloud storage
Update 6/10/2013: https://copy.com/e6LQelLOusIN
Newest is called HTC Eris Beats 11, I presume, enjoy.
(Now I come to realize that once you sign into Google Play, force closes will concur. Unfortunately up until now I could not fix, it could be evaded by not registering Google Play or if you have registered already then just disable sync in "Settings>Accounts&Sync" I apologize for any inconvenience "
No need to flash gapps.
Just wipe dalvik x3 then wipe data.
Then flash.
Extraneous Post
Update!
cm-7-20130301-NIGHTLY-desirec, enjoy
Updated the market once again; and a few minor tweaks as well.
Same concept as the predating release.
Enjoy.
Beats column just a modification in the system to have better sound, discrepant from the original Abridged Rom; same base, everything. Just the Beats Audio is irrelevant to the initial.
(MOD)Beats Audio(2.3+up) by RockoDev; credit to him. It was referred by Izeltokatl, thanks.
Link:http://forum.xda-developers.com/showthread.php?t=1525226
Aw heck I'll give it a shot. Downloading now.
Demache said:
Aw heck I'll give it a shot. Downloading now.
Click to expand...
Click to collapse
Thanks
MrSpartan said:
Thanks
Click to expand...
Click to collapse
Just give me a little bit since I accidentally ran the battery into the ground. I want to give it enough charge so it doesn't die half way through boot.
Just giving it a little break in. Not bad.
Although, I seem to have created a slight issue here, where I doubled the lockscreens.
{
"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'm assuming the ICS themed lockscreen runs independently of the normal lockscreens?
EDIT: I figured it out. I missed a line about Holo locker in your instructions.
Demache said:
Just giving it a little break in. Not bad.
Although, I seem to have created a slight issue here, where I doubled the lockscreens.
I'm assuming the ICS themed lockscreen runs independently of the normal lockscreens?
EDIT: I figured it out. I missed a line about Holo locker in your instructions.
Click to expand...
Click to collapse
Thank you very much for trying it out. Also, thanks for your compliment, it really means a lot to me.:highfive:
MrSpartan said:
Thank you very much for trying it out. Also, thanks for your compliment, it really means a lot to me.:highfive:
Click to expand...
Click to collapse
Actually, this might be a ROM that sticks around on mine for awhile. I do like how you stripped most of the phone functionality out so I don't have all that additional clutter (and possibly saving RAM? I haven't really investigated that). But hey for your first ROM, this seems to working pretty well.
Demache said:
Actually, this might be a ROM that sticks around on mine for awhile. I do like how you stripped most of the phone functionality out so I don't have all that additional clutter (and possibly saving RAM? I haven't really investigated that). But hey for your first ROM, this seems to working pretty well.
Click to expand...
Click to collapse
From what I see it does save RAM, which is crucially vital to the Eris, not only that battery durability excrescences dramatically. Which is very desirable for anyone.
I am the guy that wanted a ROM that turned the Eris into a music player. Having attempted to use TheMP3Rom, and found that it doesn't work, I am glad you made this. I am downloading it and trying it now. You have my thanks for making this happen, and I hope that the development cycle on this lasts a while, because even just the thread on that other rom is dead.
Just to clarify, that command for the battery script is "su batt-cfg" and not "su" followed by "batt-cfg" right?
Also, LOVE the boot animation. Best one I've seen. Also also, what version of CM is it based on?
Oh, one more to try on my trusty eris. I should find the beats hacks and post here, would make a fine addition to this Rom. It should work as its generic enough to work on my touchpad.
Sent from my HP Touchpad.
Izeltokatl said:
Oh, one more to try on my trusty eris. I should find the beats hacks and post here, would make a fine addition to this Rom. It should work as its generic enough to work on my touchpad.
Sent from my HP Touchpad.
Click to expand...
Click to collapse
Did you mean this? I think it only works with Sense ROMs. http://forum.xda-developers.com/showthread.php?t=1314471
Sent from my HTC One S using XDA premium.
having ordained this ROM as to what i have perceived it to be, i doth proclaim that this ROM is awesome!! :highfive:
i decided to break out the old eris to use as a spare TiVo remote around the house, and i stumble across this! great job, this is exactly what i needed to bring the eris back into rotation.
certain apps don't seem to be getting proper root access or working with superuser correctly. i don't expect to use the phone for anything other than as a TiVo remote, occasional music player, and spontaneous google searches, so i won't be using many apps that NEED root access... but that's the only "issue" i've come across. great work!
ecs1984 said:
having ordained this ROM as to what i have perceived it to be, i doth proclaim that this ROM is awesome!! :highfive:
i decided to break out the old eris to use as a spare TiVo remote around the house, and i stumble across this! great job, this is exactly what i needed to bring the eris back into rotation.
certain apps don't seem to be getting proper root access or working with superuser correctly. i don't expect to use the phone for anything other than as a TiVo remote, occasional music player, and spontaneous google searches, so i won't be using many apps that NEED root access... but that's the only "issue" i've come across. great work!
Click to expand...
Click to collapse
Thank you very much for trying it!! :highfive:
I brought an assumption that hardly nobody would try it, but I was equally mistaken.
Super_Dork_42 said:
I am the guy that wanted a ROM that turned the Eris into a music player. Having attempted to use TheMP3Rom, and found that it doesn't work, I am glad you made this. I am downloading it and trying it now. You have my thanks for making this happen, and I hope that the development cycle on this lasts a while, because even just the thread on that other rom is dead.
Just to clarify, that command for the battery script is "su batt-cfg" and not "su" followed by "batt-cfg" right?
Also, LOVE the boot animation. Best one I've seen. Also also, what version of CM is it based on?
Click to expand...
Click to collapse
Sorry for my insouciance to not get on XDA; thanks for the response and my apologies for not remembering your name.
The script is "su" for superuser permission then "batt-cfg" to execute it.
About to release an update, but this version I assume it is cm-7-20120722-NIGHTLY-desirec.
Furthermore, this will get updates, not to worry.
This is what I used on my touchpad, with cm9.
http://forum.xda-developers.com/showthread.php?t=1525226
And this one works too, I used both at the same time.
http://forum.xda-developers.com/showthread.php?t=1728391
Sent from my rezound
Izeltokatl said:
This is what I used on my touchpad, with cm9.
http://forum.xda-developers.com/showthread.php?t=1525226
And this one works too, I used both at the same time.
http://forum.xda-developers.com/showthread.php?t=1728391
Sent from my rezound
Click to expand...
Click to collapse
I'm sorry if I intruded with your conversation with Super_Dork_42; this seems very nice. Not only that, as your predating statement, that this would be a great appendage to this rom; I might implement this . Also, thanks for your cooperation in introducing this. :highfive:
My Tracks
Thanks, Spartan, for a great little ROM! I just pulled the Eris out hoping to revive it as a companion for my bike. Works great for music - sleek & fast - however something is blocking Goggle My Tracks from installing. Not sure what it is...it installs on other GB ROMs. I tried both installing from the market (the app doesn't show up), and by sideloading the APK. No dice. Any help appreciated.
MrSpartan said:
I'm sorry if I intruded with your conversation with Super_Dork_42; this seems very nice. Not only that, as your predating statement, that this would be a great appendage to this rom; I might implement this . Also, thanks for your cooperation in introducing this. :highfive:
Click to expand...
Click to collapse
Those mods are for CM9 so you'll have to make the next one CM9 based if that's possible in order to use them.
As far as I recall, one link provided for CM9 and the other for 2.3 and further.
Sent from my ERIS using xda premium