This mod is heavily based on Cytown's Modded Phone APK, available here.
I made this for myself, but wanted to share with the world.
The main features are:
* Everything Cytown's Phone Mod has, plus:
* "Shake" Phone to answer
* "Shake" Phone to mute calls.
Todo list:
* "Shake Settings", Low, Medium and Strong shakes.
* Hang Call & Send SMS automatically with predetermined text. ("I'm in a meeting, will call back asap").
Download (Fixed urls!):
* Eclair Phone APK.
* Donut Phone APK.
For installing:
1. adb push path/to/local/Phone.apk /sdcard/Phone.apk
2. adb remount
3. adb shell
4. cat /sdcard/Phone.apk > /system/app/Phone.apk
5. rm /system/app/Phone.odex (only do this if there is a Phone.odex file, odds are there isn't one if you were using Cytown's Phone Mod previously)
Click to expand...
Click to collapse
Debugging this app: [New!]
I've gotten a lot of feedback regarding the strength required to have the phone detect the shakes.
The original code was made by Mathew Wiggins, and I've modified it to add 4 different 'shake settings', but I've noticed it isn't as reliable as Mathew's code...
I've uploaded the source, and a very simple 'sample apk' that you could try. For best results, use adb logcat.
A picture's worth a thousand words, and while I can't actually take a screenshot of me shaking the phone, and don't feel like recording a video...
{
"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"
}
New ideas and reasons why my ideas are terrible are welcome.
Like my work? Buy Cytown, Cyanogen and/or the OpenEclair team a beer! They deserve it.
I'll be posting a Changelog here. To know what version you're running, go to Settings -> Call Settings. It should display a line like "Advanced Settings v26.1-Sv3".
v26.1 is the Cytown version I based it off. Sv3 is the "Shakey version" you're currently running.
Changelog v26.1-Sv3.1 (Currently reports itself as Sv3, if you downloaded Feb 27 2010, or later, you've got the correct one)
Eclair Build:
* Tweaked accelorometer settings again. It should now work correctly.
Donut Build (Untested so far):
* Tweaked accelorometer settings again. It should now work correctly.
Click to expand...
Click to collapse
Changelog v26.1-Sv3 (Based on Cytown's versioning system, S is for Shakey!)
Eclair Build:
* Fixed accelorometer settings (Used to stay on after call hung up, not any more!)
* Changed sensitivity to higher values based on more testing.
Donut Build (Untested so far):
* Fixed accelorometer settings (Used to stay on after call hung up, not any more!)
* Changed sensitivity to higher values based on more testing.
* Should now save the settings correctly. Hopefully.
Click to expand...
Click to collapse
Changelog v26.1-Sv2 (Based on Cytown's versioning system, S is for Shakey!)
Eclair Build:
* Shake to Answer
* Shake to Mute
Donut Build (Untested so far):
* Shake to Answer
* Shake to Mute
Click to expand...
Click to collapse
http://github.com/Nushio/Phone_eclair
The download link, just leak from first post.
I would like to be the first to ask for this on donut, sounds like a quality app and the todo list if you manage them all will make this amazing
Also on a side note this should be in the apps & games section
I just forked Phone_Donut and will start the Shake to Answer and Shake to Mute later for it.
As for the "Hang up call and send sms"? I was thinking on adding a separate slider to send that on Eclair, but Donut has no sliders. Ideas?
Edit: Oh, and thanks funbacon for posting the link.
I'd appreciate it if a Mod reviewed my account soon
Nushio said:
I just forked Phone_Donut and will start the Shake to Answer and Shake to Mute later for it.
As for the "Hang up call and send sms"? I was thinking on adding a separate slider to send that on Eclair, but Donut has no sliders. Ideas?
Click to expand...
Click to collapse
I've never used an Eclair rom so no idea what the sliders are but was thinking maybe an on screen option rather than the answer option some modded phone.apk's have. Or possibly menu option?
Maybe someone with more Eclair experience would be better placed to answer this for you?
Holy crap this would be pretty sick to have on my phone. So, I will be the second to ask for it.
And as for the slider. There is already two sliders on the lock screen(unlock and mute phone) and as well for the answer call screen ( answer and and mute) So what exactly are you asking about the slider on the eclair rom?
As for the Apps and Games? I posted this here, since that's where Cytown's Modded Phone app thread was, but if someone could move it, I wouldn't mind.
And yeah, I was thinking something along the lines of holding the "hang call" button 3-4 secs, but I'm not yet sure if that's even possible.
I could do on screen buttons as well.
The slider on Eclair ? I was thinking on moving the hang up call a few dozen pixels down, and placing another "hang call & sms" slider slightly above the other hang call slider, but ideas are welcome.
R
Nushio said:
As for the Apps and Games? I posted this here, since that's where Cytown's Modded Phone app thread was, but if someone could move it, I wouldn't mind.
Click to expand...
Click to collapse
Your right, my bad
Add [Mod] to your title, stop anyone else thinking its an app
I'd like to install it but I'm on MghtyMax ROM (1.5 I think), too bad
Added Donut Build. It is currently untested, so please report any issues.
I guess I'll need to buy a secondary Android device to test my stuff, since I can't go around flash CyanogenMod to OpenEclair every time I want to try something new
Edit: I'll see what I can do about Cupcake, but I think Cupcake's really pushing it, I'd rather not maintain several branches for a mod. I'd rather add more things than spend my time porting to Donut, Cupcake, etc.
Nushio said:
Added Donut Build. It is currently untested, so please report any issues.
I guess I'll need to buy a secondary Android device to test my stuff, since I can't go around flash CyanogenMod to OpenEclair every time I want to try something new
Edit: I'll see what I can do about Cupcake, but I think Cupcake's really pushing it, I'd rather not maintain several branches for a mod. I'd rather add more things than spend my time porting to Donut, Cupcake, etc.
Click to expand...
Click to collapse
Hey Nushio i would more than willing to use my Droid as a test subject for dount builds, saving you the hasslle in buying a new device.
Nice mod dude keep up the good work will post back any bugs or ideas.
Hey MrLBrick,
You use your Moto Droid with Donut? Or did you mean "Droid" as in "Android" in general?
Anyways, I got "Shake to Mute" up and working on Eclair, will port to Donut later tonight.
It is currently possible to both "Shake to Mute" and "Shake to Answer" at once, though Mute has a lower sensitivity level. I'd recommend you only select one.
I'll work on letting the user pick his sensitivity setting before going into "Hold Hang Call button to send sms"
Do You Have Any Screen Shots
oMszKikiIzWavyo said:
Do You Have Any Screen Shots
Click to expand...
Click to collapse
Uhm, What would I screenshot? The Settings panel?
I can't actually screenshot "shaking" to answer or mute. And I currently haven't done any actual modifications to the phone screens.
Nushio said:
Uhm, What would I screenshot? The Settings panel?
I can't actually screenshot "shaking" to answer or mute. And I currently haven't done any actual modifications to the phone screens.
Click to expand...
Click to collapse
O Okay And By The Way This Is A Wonderful App
Keep Up The Tremenduos Work
Nushio said:
Hey MrLBrick,
You use your Moto Droid with Donut? Or did you mean "Droid" as in "Android" in general?
Anyways, I got "Shake to Mute" up and working on Eclair, will port to Donut later tonight.
It is currently possible to both "Shake to Mute" and "Shake to Answer" at once, though Mute has a lower sensitivity level. I'd recommend you only select one.
I'll work on letting the user pick his sensitivity setting before going into "Hold Hang Call button to send sms"
Click to expand...
Click to collapse
Droid in general, sweet dude let us know and ill download and do some more test for ya
MrLBrick said:
Droid in general, sweet dude let us know and ill download and do some more test for ya
Click to expand...
Click to collapse
Ported Eclair's "Shake to Mute" back to Donut. Enjoy!
Ok Nushio 1.6 Bug Test report:
Firmware: CM-4.2.14.1
Base: 1.6
*Ignore last post ya updated it faster then i could test.
*Previous bug Not being able to select has been fixed.
*Confirmed working CM latest Dount build 4.2.14.1
*Gonna test other dount builds.
Nice work Nushio
Damn, but I think you have an "old" version. Could you check if it says "Advanced Settings V.22.3-Sv2" ?
Easiest way to know for sure, is if it has "Shake-to-Mute".
Related
EDIT: Updated 5/27/10, all mods posted here ARE compatible with the latest 2.1 deodexed release EXCEPT the no haptic feedback option listed under EDIT 4 at the end of this post. For a no haptic version compatible with Fresh 2.1.2 (or similar deodexed ROM), see here.
Though not necessarily my goal, I seem to be focusing on lockscreen mods/fixes lately. Not that I want to be known just for lockscreens, but hey, I give the people what they want .
See bottom of post for MetaMorph versions to make it easier to apply without affecting existing modifications.
I saw some chatter here about the Android 2.0 style rotary / dial lockscreen (see here), that got replaced with the current Android 2.1 style sliding tabs lockscreen, and figured it would be fun to take a look and see what may be involved in trying to port it over to our current build. Turns out, after some intensive code modifications, I was able to successful port it over .
Following are screenshots, and a link to a video, showing the "rotary" version of the vanilla lockscreen in action:
{
"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"
}
The video demo is jittery, as the screen capture couldn't keep up with the rotation. You won't actually experience this "jitter" in real-time:
Video Demo
This version of the vanilla lockscreen also contains the fixes for menu key unlock disable, removal of emergency call button after airplane mode (thanks flipz), and removal of the emergency call button on the footer of the keypattern unlock screen.
If you are currently running the stock HTC Lockscreen, you will need to move your HTC Lockscreen out of the way, via adb, so that the vanilla lockscreen is used instead, by doing the following:
Code:
adb remount
adb shell
cd /system/app
mv HtcLockScreen.apk HtcLockScreen.bak
exit
The attached flashable zip is currently the "stock" version of the lockscreen (including the fixes referenced), however, I will also soon be posting textless and custom wallpaper versions, similar to the vanilla Android 2.1 lockscreen mods I posted previously.
You can flash the attached zip from recovery without fear of undoing any other customizations or themes you may have applied, since it only includes the 'android.policy.jar' file. My starting point was Fresh 2.0d, but this should work on any Sprint leak based ROM.
You may also want to flash flipz's zips for the alarm clock issues with vanilla style lockscreens. I have not tested this and do not know if the same issues exist with this version. I am assuming they do.
Note: MetaMorph tends to have trouble applying changes to multiple framework files in a single morph, which this mod includes, and as such, applying the MetaMorph may require multiple tries. If your phone freezes / reboots when attempting to apply the final step, it may come back up with only some of the mod/theme applied (you'll still see the black taskbar). If this is the case, apply the MetaMorph again, this time, only selecting the final sub-theme, 'framework-res.apk'.
Download Android 2.0 Vanilla Rotary Lockscreen <--- Flash via recovery
NOTE: Since this replaces a framework file, your first reboot will take some time, as your Davlik cache will be rebuilt. Don't panic .
EDIT 1: See this post to download MetaMorph updates for applying different backgrounds to the stock rotary lockscreen WITH carrier / time / date text.
EDIT 2: See this post to download MetaMorph updates for applying different backgrounds to the rotary lockscreen WITHOUT carrier / time / date text.
EDIT 3: See this post to download a MetaMorph update to clear out the direction arrows if you do not want them. Apply this ONLY after first applying your desired lockscreen version.
EDIT 4: See this post to remove the haptic feedback after having first flashed your desired rotary version above.
JsChiSurf said:
Though not necessarily my goal, I seem to be focusing on lockscreen mods/fixes lately. Not that I want to be known just for lockscreens, but hey, I give the people what they want .
I saw some chatter here about the Android 2.0 style rotary / dial lockscreen, that got replaced with the current Android 2.1 style sliding tabs lockscreen, and figured it would be fun to take a look and see what may be involved in trying to port it over to our current build. Turns out, after some intensive code modifications, I was able to successful port it over .
Following are screenshots, and a link to a video, showing the "rotary" version of the vanilla lockscreen in action:
The video demo is jittery, as the screen capture couldn't keep up with the rotation. You won't actually experience this "jitter" in real-time:
Video Demo
This version of the vanilla lockscreen also contains the fixes for menu key unlock disable, removal of emergency call button after airplane mode, and removal of the emergency call button on the footer of the keypattern unlock screen.
For information on moving the stock HTC lockscreen out of the way, in order to use the Android vanilla lockscreen, please see my previous thread where instructions are posted.
The attached flashable zip is currently the "stock" version of the lockscreen (including the fixes referenced), however, I will also soon be posting textless and custom wallpaper versions, similar to the vanilla Android 2.1 lockscreen mods I posted previously.
You can flash the attached zip from recovery without fear of undoing any other customizations or themes you may have applied, since it only includes the 'android.policy.jar' file. My starting point was Fresh 2.0d, but this should work on any Sprint leak based ROM.
You may also want to flash flipz's zips for the alarm clock issues with vanilla style lockscreens. I have not tested this and do not know if the same issues exist with this version. I am assuming they do.
This should be considered a very preliminary version, and things may unwittingly break, but it seems to be working fine for me. Please report any issues you may have, and ALWAYS nandroid before flashing.
Download Android 2.0 Vanilla Rotary Lockscreen
Click to expand...
Click to collapse
man i am stoked to even think this is gonna work. flashing in a min and will let u know
First! Good work John!
SWEET. Thanks Alot.
just flash and it didnt work. took forever to load so guessing it deleted delvik on its own. any suggestions
cbarlan said:
just flash and it didnt work. took forever to load so guessing it deleted delvik on its own. any suggestions
Click to expand...
Click to collapse
I'll need more detail than that. What by didn't work do you mean? What does your logcat say? It'll definitely take a while to boot, as a framework change will cause a cache rebuild.
Worked for me. Actually, I pushed android.policy through adb.
VinceOB said:
Worked for me. Actually, I pushed android.policy through adb.
Click to expand...
Click to collapse
yeah sorry got it to work
lovin it btw
cbarlan said:
yeah sorry got it to work
lovin it btw
Click to expand...
Click to collapse
What was the problem? Want to make sure nobody else has a similar issue.
cbarlan said:
lovin it btw
Click to expand...
Click to collapse
Thanks. My favorite part is how the dial spins around when you turn volume on/off.
Oh sweet!! I have been waiting for this!!! Your the best!!!
JsChiSurf said:
What was the problem? Want to make sure nobody else has a similar issue.
Click to expand...
Click to collapse
dont really know. I wiped dalvik then reflashed and it work no problem.
JsChiSurf said:
Thanks. My favorite part is how the dial spins around when you turn volume on/off.
Click to expand...
Click to collapse
that is a sweet feature. any way of getting the time and date of off there though
cbarlan said:
any way of getting the time and date of off there though
Click to expand...
Click to collapse
Certainly. You'll see in the OP that the initial release is the stock version. I'll knock out the textless and wallpaper versions tomorrow .
Friggin awesome!!!!!!!!!!!!
Good work
toastcfh said:
Friggin awesome!!!!!!!!!!!!
Good work
Click to expand...
Click to collapse
Thanks Toast. Means a lot coming from you .
JsChiSurf said:
Certainly. You'll see in the OP that the initial release is the stock version. I'll knock out the textless and wallpaper versions tomorrow .
Click to expand...
Click to collapse
sweet...thanks man
Anyway you can port the Xperia X10 lockscreen over? ;o
Will there be a metamorph for it as well?
OtisFeelgood said:
Anyway you can port the Xperia X10 lockscreen over? ;o
Click to expand...
Click to collapse
I honestly don't even know what an 'Xperia' is...
kratos313 said:
Will there be a metamorph for it as well?
Click to expand...
Click to collapse
I'll definitely do MetaMorphs for the textless & wallpaper versions, as this affects other framework files that you may already have done customizations to.
However, for this "stock" version, a MetaMorph is not necessary, as it will NOT affect any other changes you've made in any way. It will simply replace the standard Vanilla lock screen with the Rotary version.
Alright guys, I told you I was working on a new rom. I'm happy to finally release an Android Open Source Project (AOSP) based rom. I've teamed up with Bcnice20, I'm sure ya'all know him from working on the MIUI port for the Evo. The two of us are going to be maintaining and updating this ROM.
First lets start off with....
Acknowledgements
First of all this would have not been possible without the Cyanogen Mod team. They're hard work made compiling this possible, also some of the basic fixes to the AOSP source for the Evo.
Click to expand...
Click to collapse
l33tlinuxh4x0r for posting the original "How-to" to get started from.
wrx4memp for his awesome graphix workings.
toastcfh for the kernel
kmobs for the Rotary lockscreen code.
There's been quite a few people that I've peeked on their github just to learn a few things here and there. Whether I've used any of their code or not, I'd like to acknowledge them at the very least for giving us some insight into Java/Android. Those include...
Click to expand...
Click to collapse
(These are their github accounts, not sure if this is their xda nicks.)
Wysie
cytown
leonnib4
This acknowledgement list will be updated constantly. Anyone that has a role in anything bc or myself learn or work they share with us, deserve a mention. Please do not hesitate to PM myself or bcnice20 if you feel you were overlooked.
Please make sure you have the following.
an Evo 4G
Fully Rooted
NAND Backup before any flashing!
Wipe Everything, including SD:Ext Partition (where applicable)
Now for the Goodness.
{
"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"
}
/Basic Ingredients
Android Open Source Project (AOSP) Based rom. Completely compiled by myself every release.
FRG83 / Android 2.2.1 Based.
Rooted.
Native Wireless/Wired tether capable (settings).
Custom font bundled with all Evervolv roms - Sony Sketch.
Bundled with toastcfh's CM-Kernel 2.6.35 test kernel. (give this a try and let me know what ya'all think.)
CM6.1's Camera
/Customizations
Added normal reboot and reboot to recovery in power options menu. (This will be replaced with a seperate dialog box. Did this temporarily.
Launcher2 with new and ever-improving UI!
A2SD & Dalvik2SD (Please see workaround for activating these features.)
See Changelog for more.
/Added Apps
Sprint VVM (Yes it works!!!)
XDA App
ES File Explorer
Chrome 2 Phone
Barcode Scanner
/What does not work....
4G
HDMI
9016 Message for Voicemails.
Large MMS-Videos *Unconfirmed
/Predictive Q&A - minus the Q.
This is not a sense rom, and will never be.
Please see "/What does not work...." section of the OP.
A theme is OTW, feel free to try a CM theme and report back.
/Downloads
Evervolv-AOSP v0.4.2b (BcBlends Download)
Evervolv-AOSP v0.4.1 (BcBlends Download)
Evervolv-AOSP v0.4 (BcBlends Download)
Evervolv-AOSP v0.3 (BcBlends Download)
Evervolv-AOSP v0.2 (BcBlends Download)
Evervolv-AOSP v0.1 (Wackynoodle Download)
Reserved
Changelog...
v0.4.2b
Fixed lockscreen switching issue with phone. *me - this is a workaround that just kills the phone process so it has to reload.
Made Launcher dynamically load icons for each hotseat, instead of preset drawables. *me
Changed Launcher layout to something a little better looking. This is still a huge work in progress, trying to set it up for a highly customizable launcher.
Changed a few other minor things to get this thing building for the Droid Incredible. All versions will reflect the same, except most inc roms will be alpha's.
Changed/Added default wallpaper to an Evervolv Wallpaper. * thanks a lot to wrx4memp
v0.4.1
Fixed Bluetooth.
v0.4
Added option for rotary dial lockscreen *Kmobs
Added rotary dial call answer screen (enabled when rotary lockscreen is, Still buggy.... a reboot is required when changing or it will FC when a call comes in.)*Coded by me with the help of Kmobs original lockscreen mod.
Started more customizable options (non-functional right now) *me
Added CM's reboot option temporarily. I really want to make this look unique so it will change soon enough. *CM team
Changed string for reboot in the Phone Options menu to say "Reboot Options" *me
Added CM's Phone and Contacts in an effort to get Facebook contacts to sync... Still working on this guys. *CM team
Added menu icons for Launcher menu. *Google Images is my friend! Credit to the unknown authors.
Made expanded notification bar background transparent. *me
Did some fixing in the Boot.img / Ramdisk. *me
Found a missing jar that was suppose to be included with the GAPPS (com.google.android.maps.jar). Not sure why this wasn't but it is now! *me
v0.3
Changed to Launcher2 *Google
New UI for Launcher - This is in the development stages, many of the UI elements are not as they should be. i.e icons *Coded by me
Added EVParts - Settings app for some of the settings that I will be making User-Customizable. This is based off of googles Spare Parts app. Also in development stage (can be accessed in Settings > Evervolv Settings. * Thanks google.
Made the lockscreen carrier caption User-Customizable. (Settings > Evervolv Settings > Lockscreen Settings) *Coded by me.
Changed Settings icons to some that look a lot more appealing! * Google is your friend to find small images! Found all these from random sites.
v0.2
Changed battery icon to AOSP, w/ percentage.
Changed order of Settings to be a little more aesthetically pleasing.
Added item under "About Phone" settings to show Rom Version.
Issues/Workarounds
Apps2SD/Dalvik2SD Workaround
Download a terminal emulator or Use ADB Shell to administer these commands
Code:
a2sd reinstall (it will run and then want to reboot)
a2sd cachesd (again it will want to reboot)
a2sd check (this will tell you if it worked correctly)
Sorry if im vague in this. Wrote this real quick with the wife nagging in the background.
Click to expand...
Click to collapse
Location/GPS fix for some Apps.
Goto
Code:
Settings > Location & Security > My Location > Uncheck "Use wireless networks"
This will force the phone to use the GPS instead of cell towers. This should take care of the GPS/Location issues that people found in various apps that depend on GPS location.
Click to expand...
Click to collapse
misc. Reserved
misc. Reserved...
Looks interesting. I will give it a try. Thanks.
Going to download now, and flash afterwards. let you know what i think!
atapia984 said:
Looks interesting. I will give it a try. Thanks.
Click to expand...
Click to collapse
TRUST,, you are going to want to try this! Very fast! and stable! deff good for daily use! I prefer a better kernel,, yet the one that is baked in is good! i am a OC'inf freak though! Thanks Drew for you evervolv,, that has deff evervolved! Also mad shout out to BCnice20! You all make good partners! i look forward to seeing some theme/mods and frame work tweaks! i have got to learn how to use metamorph! lol
Nice work I was kind of sad when you drop the sense rom anyways this is good and bnice too that's really cool sorry but Im not feeling the battery icon any link to the asop one?
Sent from my PC36100 using XDA App
Awsome rom!!! Where do i go to delete all the wallpapers or put my own?
thanks.
Awesome rom.....is there a way to get the stock font back??
Sent from my PC36100 using XDA App
jgalan14 said:
Nice work I was kind of sad when you drop the sense rom anyways this is good and bnice too that's really cool sorry but Im not feeling the battery icon any link to the asop one?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm actually going to go to an AOSP looking one with percentage. I put that in there because I liked it... awaiting a different theme. I'll put an update out tomorrow or the next.
Also, any update will most likely be a FULL update, unless its just to patch an error or something. When compiling from source.... the resource ID's (strings, arrays, drawables, etc...) are created at the time of compiling. So if theres any changes to these, all the files that reference them will need to be replaced. Unfortunately any themes from CM most likely wont work for this rom either. Unless you were to replace only the images in the framework-res.apk.
preludedrew said:
I'm actually going to go to an AOSP looking one with percentage. I put that in there because I liked it... awaiting a different theme. I'll put an update out tomorrow or the next.
Also, any update will most likely be a FULL update, unless its just to patch an error or something. When compiling from source.... the resource ID's (strings, arrays, drawables, etc...) are created at the time of compiling. So if theres any changes to these, all the files that reference them will need to be replaced. Unfortunately any themes from CM most likely wont work for this rom either. Unless you were to replace only the images in the framework-res.apk.
Click to expand...
Click to collapse
Cool thanks for the info and probably will get gingerbread lol
Sent from my PC36100 using XDA App
really nice looking rom, do you think the snap turbo kernel will work with this?
This is just my 2cents, but just keep it simple the way it is. If anything make performance tweaks and whatever you can add/do to help the battery consumption. Remove anything that's not necessary to boot up the system and run it, if we want something extra we can always download it and add it to it. Looking for the donate...
Thanks
preludedrew said:
I'm actually going to go to an AOSP looking one with percentage. I put that in there because I liked it... awaiting a different theme. I'll put an update out tomorrow or the next.
Also, any update will most likely be a FULL update, unless its just to patch an error or something. When compiling from source.... the resource ID's (strings, arrays, drawables, etc...) are created at the time of compiling. So if theres any changes to these, all the files that reference them will need to be replaced. Unfortunately any themes from CM most likely wont work for this rom either. Unless you were to replace only the images in the framework-res.apk.
Click to expand...
Click to collapse
Deodexted? I assume so, since you mentioned a theme but it does not specify anywhere. Just curious. I wanna flash the stock fonts. Im eager to try this ROM.
Nice to see some more AOSP ROMs on the Forums. Before the next MIUI Update i'll be sure to try this out.
I'm really suprised that this rom is not getting more attention, ITS AMAZING!! Very fast and very stable so far since I have been using it. My only complaint is that damn battery icon, just cant get used to it . Anyways I've used this rom with netarchy univ, zendroid, and kings kernels and they all work great!! Kings gives me great battery life with your rom and so far is the best aosp for batter life in my case. Also get some good quadrant numbers with zen's. Anyways awesome rom and I cant wait to see how you improve it
Sent from my PC36100 using XDA App
0.2 is UP!
Evervolv-AOSP v0.2 is UP! You should be able to flash this on top of v0.1, however wipe cache and dalvik to make sure. If it boot loops, do a full wipe.
0.2
Changed battery icon to AOSP, w/ percentage.
Changed order of Settings to be a little more aesthetically pleasing.
Added item under "About Phone" settings to show Rom Version.
7/21/11 Update: RandomKing has ported this mod to EF02. It's available here. Thanks!
Attached is a platform source patch against android-cts-2.2_r2 that modifies the ringer volume control (side rocker) to include both vibrate & silent options, as was present in Eclair. Also attached is a smali patch against EC05's /system/framework/framework.odex that implements the fix in bytecode.
Finally, attached are testkey-recovery (e.g., ClockworkMod) flashable "update.zip"s, one containing a modified framework.jar for deodexed ROMs, the other containing a modified framework.odex for odexed (stock) ROMs. Both updates include this modification, as well as the TWS bug fix.
I've tested the odex update under stock (w/testkey) recovery, but not ClockworkMod as I currently don't use it, although I imagine it works fine. I've not tested the deodex update as I run an odexed ROM (edit: others report it works too). I have no reason to suspect it wouldn't work, but the usual caveat of keeping a copy of Odin+tar, ClockworkMod backup, etc., to restore should something unexpected happen applies.
Edit: If you're running a custom ROM with other framework.jar changes, it's probably best to wait for that ROM to incorporate the patch.
Background:
The Eclair ringer volume control (popup on press of the side volume rocker) contains "ringer vibrate" and "ringer silent" options. In Froyo, this was simplified to a single "ringer vibrate" or "ringer silent" option, depending on the Vibrate setting (Settings -> Sound -> Vibrate). While perhaps conceptually simpler, this has upset some folks who make frequent use of both options, as it requires going into the Settings and fumbling around with a control that really isn't that intuitive to begin with.
Behavior:
This modification doesn't quite restore Eclair behavior, rather it depends on the Vibrate setting. When Vibrate is set to "Always" or "Only in silent mode", both vibrate & silent options are available in the ringer volume control; otherwise, the default "Silent mode" option (Settings -> Sound -> Silent mode, power long-press, or notification panel widget) is still to vibrate. When Vibrate is set to "Never" or "Only when not in silent mode" then the default Froyo behavior is preserved: only silent is available in the ringer volume control, and "Silent mode" always silences (not vibrates) the ringer.
The modification is implemented this way as to be inoffensive to folks who dislike the vibrate option, and never under any circumstance would want their phone to accidentally vibrate. Similarly, it should be mostly inoffensive to folks who always prefer the vibrate option--the only way to activate the silent ringer is by the volume down rocker. So, as long as folks are careful to not accidentally press volume down "too many times", this modification is strictly beneficial (and thus, it's inclusion in ROMs shouldn't be of significant debate ).
Detials:
With regard to the code: while Froyo simplified the vibrate/silent options in the UI, it's actually gotten a bit more complicated in code. With regard to the ringer, there's three state variables influence what happens. AudioService#mRingerMode is the main variable, with options RINGER_MODE_NORMAL, _VIBRATE, and _SILENT. AudioService::checkForRingerModeChange is the method that implements the volume rocker logic, and setting the ringer mode to one of the above three options is all that's necessary to achieve the desired effect.
The second influential variable is AudioService#mVibrateSetting which indirectly determines when the phone should vibrate. It's not to be queried directly however, rather AudioManager/AudioService::shouldVibrate considers both the Vibrate setting and the ringer mode. Specifically, RINGER_MODE_SILENT should override any instance of a ring or notification vibrate. This is why setting RINGER_MODE_SILENT is sufficient to silence the phone without also having to change the Vibrate setting. Even though the Froyo UI forces one to this, the Eclair behavior is, fortunately for this modification, still preserved in code.
Finally, the third variable, which is new in Froyo, is System.VIBRATE_IN_SILENT (via content provider). It's set by SoundSettings::setPhoneVibrateSettingValue as a function of the Vibrate setting ("Always", "Only in silent mode" are true; "Never", "Only when not in silent mode"" are false) and updated concurrently with it. Normally the ringer volume control queries this variable to determine which "silent" ringer mode to enter. With the modification, this variable is queried to determine if "ringer vibrate" should be presented as an option, and if so, allows for either mode. It's also used by other methods (e.g., Settings -> Sound -> Silent mode) to determine which ringer mode to enter, which isn't altered by the modification.
For the modification, I did consider always presenting "ringer vibrate" and "ringer silent" options, updating VIBRATE_IN_SILENT as necessary so that other activations of "Silent mode" would use the previous setting. But the SoundSettings activity actively updates the Vibrate setting whenever the two variables are in conflict, which would result in a bit of behavioral confusion. It's simpler, both conceputally and in code, to leave it alone.
Anyways, I figured it was worth documenting the behavor here since there's a bit more that goes on behind the scenes than the relatively-simple modification would suggest. I'm not sure which, if any of this changes in Gingerbread. But if the semantics were changed significantly, that might make a port of this modification a little less obvious.
Mirror link (does not require forum login):
platform_ringer_vib_silent.diff
platform_ringer_vib_silent_smali.diff
tws_fix_ringer_vib_silent-EC05-deodex.zip
tws_fix_ringer_vib_silent-EC05-odex.zip
Deodexed tested...consumer approved awsome job! The vibrate function is working as intended.
Dude from mod to mod you are awesome. Can we have a progress log of what you are gonna try next lol.
Sent from my SPH-D700 using XDA App
You're amazing! Any more progress on the keyboard patch??
Sent from my SPH-D700 using XDA App
YES!
Sent from my SPH-D700 using XDA App
Wow you never stop. Awesome work.
Sent From My Evo Killer!
So I flashed the zip for deodexed roms first. Didn't work for me. Then, I flashed the zip for odexed roms. Still doesn't work. Do one of you guys know what I am doing wrong?
Edit: Oh yeah, I'm on an EB13 based rom. I guess that's the problem?
Custodian said:
Deodexed tested...consumer approved awsome job! The vibrate function is working as intended.
Click to expand...
Click to collapse
Great, thanks for testing!
jbadboy2007 said:
Can we have a progress log of what you are gonna try next lol.
Click to expand...
Click to collapse
I don't like to make promises, just in case it takes a long time or I can't figure it out. Although if I make enough progress on an issue I'd probably at least post my thoughts so other folks can continue the work.
qbking77 said:
Any more progress on the keyboard patch??
Click to expand...
Click to collapse
Not yet, I had to step away from it for a bit to think.
running_the_dream said:
Do one of you guys know what I am doing wrong?
Click to expand...
Click to collapse
Which ROM are you running?
Not working here either. Flashed the deodexed version on Syndicate 1.1.0 with no change. Tried toggling the Vibrate option in Settings as well.
Which ROM are you running?[/QUOTE]
I'm on UrbanLegend rom codename: Red Beast v. 0.1a
ragnarokx said:
Not working here either. Flashed the deodexed version on Syndicate 1.1.0 with no change.
Click to expand...
Click to collapse
You might have to clear the dalvik-cache for it to take effect. However, I'm fairly certain that SRF comes with other framework changes which this would undo. It's probably best to wait for k0nane to incorporate it in the next SRF release.
running_the_dream said:
I'm on UrbanLegend rom codename: Red Beast v. 0.1a
Click to expand...
Click to collapse
Yeah, likely the same thing. Probably best to wait for it to be pulled into the ROM, or patch the ROM's framework.jar/classes.dex yourself.
I'll start a $10 bounty for getting the tv out functionality to work!
Sent from my SPH-D700 using Tapatalk
mkasick said:
You might have to clear the dalvik-cache for it to take effect. However, I'm fairly certain that SRF comes with other framework changes which this would undo. It's probably best to wait for k0nane to incorporate it in the next SRF release.
Click to expand...
Click to collapse
Still a no go with wiping dalvik-cache. Thanks anyway, will wait for ROM incorporation.
mkasick said:
Yeah, likely the same thing. Probably best to wait for it to be pulled into the ROM, or patch the ROM's framework.jar/classes.dex yourself.
Click to expand...
Click to collapse
Rats, I have no idea how to patch the framework in order to incorporate this fix. Maybe I'll try to brick my phone tonight if I get the chance. Thanks for the follow up.
running_the_dream said:
Rats, I have no idea how to patch the framework in order to incorporate this fix.
Click to expand...
Click to collapse
It's not terribly difficult if you're a bit familiar with a command line.
You need a copy of smali (the two jar downloads) and a copy of /system/framework/framework.jar from your phone (for deodexed ROMs). You'll also need the "patch" program, which typically comes with development packages for Mac & Linux. On Windows, you can get it with Cygwin, make sure to select the "patch", "zip" & "unzip" packages (if they're separate, going from memory from a long time ago). You'll also need the Java JRE if you don't have it already.
Then put all the smali downloads, framework.jar, and the platform_ringer_vib_silent_smali.diff patch all in the same directory. Then pull up a command line shell (e.g., Cygwin) and run:
Code:
java -jar baksmali-1.2.6.jar framework.jar
cd out; patch -p 1 < ../platform_ringer_vib_silent_smali.diff; cd ..
java -jar smali-1.2.6.jar -o classes.dex out
zip -9 framework.jar classes.dex
Then you can replace /system/framework/framework.jar in the update.zip with the new copy and it should work.
At least, that's the general idea.
mkasick said:
It's not terribly difficult if you're a bit familiar with a command line.
You need a copy of ...Then you can replace /system/framework/framework.jar in the update.zip with the new copy and it should work.
At least, that's the general idea.
Click to expand...
Click to collapse
Awesome! I do have Jave JRE. I can extract the framework.jar and make a test copy of it. I'll look into Cygwin and do a lil research on it. Will report back if I can get this thing going. Thanks!
I didn't exactly want a progress log exactly. But I would like to know what other things you might consider taking a look at so if people have any suggestions or something.
Sent from my SPH-D700 using XDA App
Gonna take some work looking up how to actually work with Cygwin. I'll get there Thanks again.
mkasick...
{
"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"
}
Out of curiosity, are you making your edits in Java, recompiling, then pulling the smali out and using it for the diffs, or editing the existing smali directly?
mkasick said:
It's probably best to wait for k0nane to incorporate it in the next SRF release.
Click to expand...
Click to collapse
For once, someone assumes something about me or what I'm going to do and hits a bullseye.
CyanogeMod 10.1 for HTC ChaCha [a810e / Status]
DISCLAIMER :
Click to expand...
Click to collapse
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this ROM before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh.
* make sure you do a nandroid backup in case your phone blows up in
* your face because your phone cant handle the speed :).
*/
* CREDITS
Click to expand...
Click to collapse
Code:
Google
Android
CyanogenMod
androidarmv6
OWLProject
Andreas Schneider
Special thank to winsuk
Special thank to JDevs (kernel,Device & Vendor,bug fixed,guide,support)
alquez
Droste
pabloPL
WFS: crossfire77 rallapag
ChaCha: adumont (patches Lucas Arran
everyone who's been working on CM10.1
And you!
WORKING
Click to expand...
Click to collapse
Code:
- GSM
- Data (2G/3G)
- SMS / MMS
- GPS ???
- USB
- Bluetooth
- WI-FI
- LED
- Camera
- Photocamera [fully]
- Camcoder (low FPS)
- Panorama mode [figured screen sometimes,It can be fixed easily]
- Video playback [not fully, with the 90º rotation playback,It can be fixed easily]
- YouTube [LQ/HQ/Browser] ???
- FM ???
??? I have not tested them
BUG:
Code:
- Battery drain fast
- Front camera
- USB Tethering
- Wi-Fi-Modem
- A2DP lag
- FM Radio
- in-call screen - caller picture is not in the right place with the right dimensions.It can be fixed easily
KERNEL FEATURES
Click to expand...
Click to collapse
https://github.com/OWLProject/OWL-Predator-KERNEL/blob/master/README.md
NO NEXT
BUT I'll upload my source files and step-by-step guide on my github(https://github.com/luzifer1984). a few days later.
I'm Chinese,so I would not compile next ROM for WWE.
My next build is only support for HTC CN CHS.
You can build a rom from source. plz add zh_CN (Chinese Simplified) support. THX!
cm-10.1-20130528-EXPERIMENTAL-chacha-A1.zip
https://docs.google.com/file/d/0B2l4GSuwT6TKMExrRXpmXzZyb3M/edit
CronMod-INT2EXT
http://forum.xda-developers.com/showthread.php?t=1716124
{
"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 havent tested this yet - I will this evening. but. if this works.. THANK YOU. I LOVE YOU SO MUCH FOR FIXING THE DIALPAD.
although I still think the "end call" onscreen button is not necessary.
We need to figure out how to map the End Call button(the red physical button) to end the call(if you havent already) and the number keys(physical keys) need to also input on the dialpad just as they do in CM9(again, havent tested yet. if they do, you're amazing. )
The "Call" or Green physical button should call the number onscreen, or from the home screen it should open the recently called list.
If you can fix all this stuff(or have already) I'll give you money. lol
Am I dreaming? This is amazing news! WOW. WOW. Great. Need to test this asap! Hopefully someone build one for us using your source. To who that would make a build for us: do not forget TURKISH language please!
---------- Post added at 06:14 PM ---------- Previous post was at 06:08 PM ----------
By the way, why not you make builds for EU, too? I mean, It shouldn't take some time for you to add a couple of more languages whenever you make a new build.
MD5sum: 5b7ccba99f8b63087696568c85070808
I didn't fix the screen layout of the dialpad. that have been fixed by CM10.1
I want to ask, are you working on front cam? All the problems other than front cam seems solvable to me.
So you have made to first custom kernel for the ChaCha?
Do you intend to work on the kernel? Because even if you don't update the ROM, but you keep the kernel source updated I can build it and make a flashable zip.
The battery life is probably a kernel issue right?
Edit: running it now. The slow wakeup bug from CM10 is fixed. Everything is great, except for battery. I hope there is a breakthrough with that. Thanks for the ROM!
kernel,Device & Vendor
Updated
luzifer1984 said:
kernel,Device & Vendor
Updated
Click to expand...
Click to collapse
So these updates include the fixes that OWLProject offers for Wildfire S? In this build of yours there is lag and now I see it is fixed in wildfire s.
Flashed this rom yesterday, looks some of the issues with CM 10 is fixed with 10.1.
If you are looking for gapps for 10.1, the slim version can be found in http://forum.xda-developers.com/showthread.php?t=2265564
I don’t see major issue with battery drain, it got discharged 25% after 12 hours of usage without wifi or data.
a) Lock screen is completely fixed with CM10.1 and fits wells within the screen
b) In call screen is neatly tailored for landscape
c) Apollo player works in landscape
Some of the things which needs fix
a) Caller id screen is overlapped, and it is very difficult see the caller info
b) Many of the popular application in playstore says ‘This item is not compatible with your device’ example ‘gmail’, ‘apex launcher ‘ etc
c) The proximity sensor is not working.
overall its superb rom, and it alomost complete rom. Thanks bro
ajeevlal said:
b) Many of the popular application in playstore says ‘This item is not compatible with your device’ example ‘gmail’, ‘apex launcher ‘ etc
Click to expand...
Click to collapse
Use any file manager, navigate to /system, look for the build.prop
Thanks to
Furkan DEĞER :
Turns out lcd density is set to 150, which should be 160. I changed it back to 160 and it solved my problem.
Click to expand...
Click to collapse
luzifer1984 said:
Use any file manager, navigate to /system, look for the build.prop
Thanks to
Click to expand...
Click to collapse
i figured that out few min back, i just changed the lcd density in build.prop and cleared the data/cache in playstore and it worked.
Thank you
furkandeger said:
By the way, why not you make builds for EU, too? I mean, It shouldn't take some time for you to add a couple of more languages whenever you make a new build.
Click to expand...
Click to collapse
Because chinese need "Lunar support"
" phoneloc (Chinese phone location) display support "
"Chinese keyboard input support by different kernel"
sorry for my english
luzifer1984 said:
Because chinese need "Lunar support"
" phoneloc (Chinese phone location) display support "
"Chinese keyboard input support by different kernel"
sorry for my english
Click to expand...
Click to collapse
Oh, I see so you have to work on a different kernel. I see. I want to ask something else. There are some lags, especially occuring in lockscreen and also on the system generally. I see in the wildfire s forums, this was a problem with the kernel and it was fixed a couple of days ago. You said you updated, kernel, device and vendor. Does that mean you applied this fix? Because, I'm setting up environment to build from your gits so, when I pulled the repo from you, will this fix be applied on the kernel?
furkandeger said:
Oh, I see so you have to work on a different kernel. I see. I want to ask something else. There are some lags, especially occuring in lockscreen and also on the system generally. I see in the wildfire s forums, this was a problem with the kernel and it was fixed a couple of days ago. You said you updated, kernel, device and vendor. Does that mean you applied this fix? Because, I'm setting up environment to build from your gits so, when I pulled the repo from you, will this fix be applied on the kernel?
Click to expand...
Click to collapse
No. I didn't merge OWL-Predator-KERNEL‘s update.
But you can check https://github.com/Luzifer1984/OWL-Predator-KERNEL/commit/b83a499dcbc60b2a18f917de5845d024d905f3f8
and you will kown how to .
just initial import from chacha-gb-crc-2.6.35-1643b58 (HTCDev.com)
luzifer1984 said:
No. I didn't merge OWL-Predator-KERNEL‘s update.
But you can check https://github.com/Luzifer1984/OWL-Predator-KERNEL/commit/b83a499dcbc60b2a18f917de5845d024d905f3f8
and you will kown how to .
just initial import from chacha-gb-crc-2.6.35-1643b58 (HTCDev.com)
Click to expand...
Click to collapse
OWL-Predator-KERNEL updating too often to catch
I wonder, can we use the kernel from the other CM10 rom? would that fix any performance issues? it would likely result in some of the things fixed to be broken again(camera? I dunno) but in terms of battery life and whatnot, I wonder if it would work
That having been said - I tried out the rom, it's very fast, smooth, it does drain the battery faster, but its not -too- bad. I think this has to do with there being no options for governor(or at least, none that I could find)
The rom has fixed most of the layout issues with the ChaCha. The dial screen is very nice, and the physical keys input once again. The lock screen fits properly now too.
I'll definitely have to do some more testing, but theres a few things that need to be fixed still. One is the LCD density in the build.prop - it causes some issues with certain apps.
EDIT: I also just noticed that while the phone is locked, the cpu must get set to a lower clock speed or something. The phone is very slow to respond when you go to unlock it.
kronflux said:
I wonder, can we use the kernel from the other CM10 rom? would that fix any performance issues? it would likely result in some of the things fixed to be broken again(camera? I dunno) but in terms of battery life and whatnot, I wonder if it would work
That having been said - I tried out the rom, it's very fast, smooth, it does drain the battery faster, but its not -too- bad. I think this has to do with there being no options for governor(or at least, none that I could find)
The rom has fixed most of the layout issues with the ChaCha. The dial screen is very nice, and the physical keys input once again. The lock screen fits properly now too.
I'll definitely have to do some more testing, but theres a few things that need to be fixed still. One is the LCD density in the build.prop - it causes some issues with certain apps.
EDIT: I also just noticed that while the phone is locked, the cpu must get set to a lower clock speed or something. The phone is very slow to respond when you go to unlock it.
Click to expand...
Click to collapse
Using kernel-kitchen you can extract the ramdisk from the CM10 boot.img and then extract the zImage from the CM10.1 boot.img and then combine the resulting zImage and ramdisk. I'm not sure if that makes sense. I'll try it sometime this weekend.
atrix4g18 said:
Using kernel-kitchen you can extract the ramdisk from the CM10 boot.img and then extract the zImage from the CM10.1 boot.img and then combine the resulting zImage and ramdisk. I'm not sure if that makes sense. I'll try it sometime this weekend.
Click to expand...
Click to collapse
well, I can't be positive as of yet, because I just installed it, but I just grabbed the CPU editor thing from here:
http://forum.xda-developers.com/showthread.php?t=1846967
I set it to On-Demand, changed the minimum frequency a tiny bit higher than the default, and set the max to 800. So far it seems like its better on the battery, but again, just installed it like 20 minutes ago, so I'll have to give it some time in testing.
kronflux said:
well, I can't be positive as of yet, because I just installed it, but I just grabbed the CPU editor thing from here:
http://forum.xda-developers.com/showthread.php?t=1846967
I set it to On-Demand, changed the minimum frequency a tiny bit higher than the default, and set the max to 800. So far it seems like its better on the battery, but again, just installed it like 20 minutes ago, so I'll have to give it some time in testing.
Click to expand...
Click to collapse
"Settings"--"About phone" AND press "Build number" 3times to enabled development settings .
then go back "Settings" ,there have show "Performance" .
AND in "Processor" you will see this rom default setting is On-Demand.
CONFIG_MSM_CPU_FREQ_ONDEMAND_MAX=800000
CONFIG_MSM_CPU_FREQ_ONDEMAND_MIN=122880
Yes, you are correct completely.
I also just noticed that while the phone is locked, the cpu must get set to a lower clock speed or something. The phone is very slow to respond when you go to unlock it."
Click to expand...
Click to collapse
that can be save power, I guess
kronflux said:
I wonder, can we use the kernel from the other CM10 rom? would that fix any performance issues? it would likely result in some of the things fixed to be broken again(camera? I dunno) but in terms of battery life and whatnot, I wonder if it would work
That having been said - I tried out the rom, it's very fast, smooth, it does drain the battery faster, but its not -too- bad. I think this has to do with there being no options for governor(or at least, none that I could find)
The rom has fixed most of the layout issues with the ChaCha. The dial screen is very nice, and the physical keys input once again. The lock screen fits properly now too.
I'll definitely have to do some more testing, but theres a few things that need to be fixed still. One is the LCD density in the build.prop - it causes some issues with certain apps.
EDIT: I also just noticed that while the phone is locked, the cpu must get set to a lower clock speed or something. The phone is very slow to respond when you go to unlock it.
Click to expand...
Click to collapse
I don't understand the "very fast, smooth" part. It is not like that for me. Rom is occasionally lagging. When scrolling especially. Sometimes it freezes completely. I believe it's kernel related.
{
"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"
}
INFAMOUS OPEN ANDROID PROJECT
AN INFAMOUS PRODUCTION
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
By using the rom you agree with the above terms!
ABOUT THE ROM:
You may be asking yourself, "What the hell is IOAP". Well, its simple really so I will keep it short and sweet. IOAP is built from source. Almost similar to AOSP with lots of added features.
FEATURES:
BT Car Fix
Dark UI
Active Display
Halo
MulitWindow
Gesture Anywhere
Appbar
LCD Density
Animation Control: System, listview, Scrolling, Keyboard, and Toast
Custom Progress Bar
Lockscreen Notifications
OmniSwitch
Recent RAM bar
Screen Record
System App Remover
Init.d
Build.prop Mods
GPS Optimizer
Navigation Bar
Expanded Desktop
Slim Recents
MORE!!!
Source:
Rom-https://github.com/IOAP
Kernel-https://github.com/CyanogenMod/android_kernel_htc_msm8960
Screenshots:
Changelog:
Code:
3/17/14 * intitial release for ville
3/18/14 * Added On-The-Go (Turn on from settings/IOAP settings/buttons/Power menu
*v3. 59
Removed GPSOptimizer
Added PACPreformance (open from settings)
Remove QuickSearchBox from build
releasetools: don't create prebuilt_dir path if it exits
av: added missing profiles
rebased: Launcher3
Added ONTHGO, powermenu and tiles (nameless)
Fixed naming convention for jflte bootlogo
Fixed some dependencies
removed paddingLeft broke build after slim card update
CM updates
Removed Bubble option in mms caused fc
Extend installd to support SELinux restorecon function
Add support for ECDSA P-256 with SHA256
libc: Fix memchr inclusion (older devices)
more fixes and tweaks than I can remember...
Downloads:
IOAP FOR VILLE
IOAP GAPPS
PA GAPPS
INSTRUCTIONS:
FULL WIPE, FLASH ROM THEN GApps
BUGS:
Code:
* You tell me
USE THIS RECOVERY
Dont forget the THANKS button
XDA:DevDB Information
INFAMOUS IOAP, a ROM for the HTC One S
Contributors
WhiTeRhiNo, mr impossible, Jamison904, mr impossible, Jamison904
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod, AOSP
Version Information
Status: Stable
Current Stable Version: 3.55
Stable Release Date: 2014-03-17
Created 2014-03-17
Last Updated 2014-03-31
Reserved
Reserved
WhiTeRhiNo said:
...
FEATURES:
BT Car Fix...
Click to expand...
Click to collapse
You got me with this one :laugh: I'll download it and try.
Also I saw that the GAPPS packages from OP are a little bit old (2013). Is there an issue if I use Slim GAPPS that are more recent? Why Slim? Because they have better compatibility with the "dark" switch
NOTE: There's a new official TWRP recovery version 2.7.0 HERE and I can confirm it is full SELinux compatible and you can flash KK ROMs with it. There's no need to use a modded TWRP recovery anymore. I am using it for some days and works great, flashed Twisted and Beanstalk with it (and now I'll try IOAP)
What you might consider adding to the ROM (if it's not already there)...Sound Packs. These are implemented in Beanstalk and provide different sound "sets" that are used for the different ROM sounds (screen lock, camera, tap and so on)
Rapier said:
You got me with this one :laugh: I'll download it and try.
Also I saw that the GAPPS packages from OP are a little bit old (2013). Is there an issue if I use Slim GAPPS that are more recent? Why Slim? Because they have better compatibility with the "dark" switch
NOTE: There's a new official TWRP recovery version 2.7.0 HERE and I can confirm it is full SELinux compatible and you can flash KK ROMs with it. There's no need to use a modded TWRP recovery anymore. I am using it for some days and works great, flashed Twisted and Beanstalk with it (and now I'll try IOAP)
Click to expand...
Click to collapse
Lol yea I remembered u. And thanks for the info I'll update op with recovery when I wake up lol
And u can use whichever GAPPS u prefer I just linked our teams GAPPS they will get updated eventually but feel free to use any they should all work fine
Edit: and I will definitely look into the sound packs and see what we can do
WhiTeRhiNo said:
...Edit: and I will definitely look into the sound packs and see what we can do
Click to expand...
Click to collapse
LOL..No need to look into it. It is ALREADY included :laugh:
What I've noticed so far:
- there are no color options for status bar items: battery, signal, clock
- there are no color options for the tiles
- there are no clock options at all: show date/AM/PM, clock color, clock position (center, right)
- even if in build.prop default screen DPI are set to 240, the look of the interface is like it is set to 200 (or something like this). Everything is smaller including status bar. I'll try to change DPI from the settings and reboot to see what's happening
- Messaging app is FC when entering in it and tapping on a message or sending a new message (this is annoying as hell for those texting a lot). Workaround: use Hangouts for SMS, that is working
- "selector notification" (also known as IME notification) ON/Off checkbox is doubled: once is present in Languages & Input and once is in Advanced Settings under Language & Input
- this is the only ROM for which Thyrus's HoloDark KK Theme (which in my opinion is the most good looking and complete dark theme out there) is theming the dialer completely including the incoming call screen. That means that the dialer is based on Carbon or Slim cause for any other dialers from any ROM I've tried, it is not properly themed (the incoming call screen has a semitransparent band on the bottom, text in the non-intrusive call is readable...and so on)
I'll add more as I test more... So far very good job :good:
---------- Post added at 12:03 PM ---------- Previous post was at 11:47 AM ----------
Rapier said:
...
- there are no color options for status bar items: battery, signal, clock
..
- there are no clock options at all: show date/AM/PM, clock color, clock position (center, right)
Click to expand...
Click to collapse
EDIT on that. Clock options (both color and position, etc) are present in Settings - Clock & Date. Not the usual place for them compared to other ROMs but they're present. Still looking for battery color
OK. Got sorted out the Messaging app FC as well. There's an option in Messaging settings to use "Speech Bubble theme". If that option is enabled (it is by default), Messaging app is FCing. Disable it and it'll work but you'll have the background white that's not so nice looking on dark theme...but that will be sorted out later
I just installed your new Rom as I was curious. All in all nice job, but I haven't tested to much. One issue is, that I get FC's, when I try to open the Dev settings.
Hi, which version of Hboot for this rom? thanks
kalel77 said:
Hi, which version of Hboot for this rom? thanks
Click to expand...
Click to collapse
2.15
Thanks for the feedback guys. All things will be improved and fixed in time. Keep the feedback coming so I know what u like and what doesn't work
derkleinebroicher said:
I just installed your new Rom as I was curious. All in all nice job, but I haven't tested to much. One issue is, that I get FC's, when I try to open the Dev settings.
Click to expand...
Click to collapse
Dont have that problem. You are talking about developer options in settings correct?
Nice rom and all i need... nice font nice design...
CRT animation in Display does not work properly. Regardless of the setting, there's only the colapse horizontal that is working
Sent from nowhere over the air..
WhiTeRhiNo said:
Dont have that problem. You are talking about developer options in settings correct?
Click to expand...
Click to collapse
Exactly! And I just made a new clean install, but with same result. Furthermore, when I tab the build number in settings and dev options are enabled, there should come something like "You are arlready a Dev." But nothing happens in this case, so for me, there is something wrong. BTW, I'm running ART, which normally should be no problem, I guess. Going to make some more inquiries and keep you informed.
derkleinebroicher said:
Exactly! And I just made a new clean install, but with same result. Furthermore, when I tab the build number in settings and dev options are enabled, there should come something like "You are arlready a Dev." But nothing happens in this case, so for me, there is something wrong. BTW, I'm running ART, which normally should be no problem, I guess. Going to make some more inquiries and keep you informed.
Click to expand...
Click to collapse
Not quite, if you're using ART it could very well be the problem. ART is experimental and it has issues sometimes. Doesn't mean that if you used ART on other ROMs without issues, you won't have issues at all with any ROM.
First, you don't need to tap several times on build number. This is needed only if Dev Options are not visible in settings but this is not the case, they are. Second, Dev Options works perfectly so you could switch to Dalvik and check again
@WhiTeRhiNo: there's another issue I found and that's related to audio libs somewhat. ONLY if using headset (wired ones not BT), if I'm in a call, the other party report that I can be barely heard, distorted and with frequent interruptions. It is not happening on normal call through handset, speaker or BT car kit. If for examplke I start the call through headset, after unplugging them all things go to normal if I continue to talk via handset. This is something I got also on TwistedKat but was not present in Beanstalk. I don't think it's kernel related because on all three ROMs I've used the same kernel with the same settings. Check with phoenixita what audio libs he's using, I'm not even sure which are used when headset is plugged in. Practically I cannot use a headset during a call because of this. I can hear perfectly, also music coming through OK, just that when I speak the other party cannot hear me well.
Rapier said:
Not quite, if you're using ART it could very well be the problem. ART is experimental and it has issues sometimes. Doesn't mean that if you used ART on other ROMs without issues, you won't have issues at all with any ROM.
First, you don't need to tap several times on build number. This is needed only if Dev Options are not visible in settings but this is not the case, they are. Second, Dev Options works perfectly so you could switch to Dalvik and check again
@WhiTeRhiNo: there's another issue I found and that's related to audio libs somewhat. ONLY if using headset (wired ones not BT), if I'm in a call, the other party report that I can be barely heard, distorted and with frequent interruptions. It is not happening on normal call through handset, speaker or BT car kit. If for examplke I start the call through headset, after unplugging them all things go to normal if I continue to talk via handset. This is something I got also on TwistedKat but was not present in Beanstalk. I don't think it's kernel related because on all three ROMs I've used the same kernel with the same settings. Check with phoenixita what audio libs he's using, I'm not even sure which are used when headset is plugged in. Practically I cannot use a headset during a call because of this. I can hear perfectly, also music coming through OK, just that when I speak the other party cannot hear me well.
Click to expand...
Click to collapse
I second the audio libs issue. I found the same problem actually. Any fix? Only work around I see is not to use my headphones in a call. My voice apparently drops in and out periodically, but I hear everything perfectly.
Sent from my One S using Tapatalk
Maybe something will be found in Beanstalk, that ROM does not have this issue. So far I found it in TwistedKat and on this one but to be honest I didn't test the headset with all the ROMs I've flashed
You asked also for suggestions what to add to the ROM. Well there are some, I'll make a list with what just crossed my mind:
- color option for battery
- lockscreen theming capabilities (lockring, colors, etc)
- tiles color settings
- add custom tile and contact tile
Rapier said:
Not quite, if you're using ART it could very well be the problem. ART is experimental and it has issues sometimes. Doesn't mean that if you used ART on other ROMs without issues, you won't have issues at all with any ROM.
First, you don't need to tap several times on build number. This is needed only if Dev Options are not visible in settings but this is not the case, they are. Second, Dev Options works perfectly so you could switch to Dalvik and check again.
Click to expand...
Click to collapse
Tapping the build number was simply to see, what happens. I know, I don't have to do this, if dev options is already enabled. And sadly, I can't switch the runtime on this Rom as long, as I can't open dev options. This will get a bigger operation. But maybe I will return to dalvik anyway as I can't see a really convincing advantage in using ART.
derkleinebroicher said:
Tapping the build number was simply to see, what happens. I know, I don't have to do this, if dev options is already enabled. And sadly, I can't switch the runtime on this Rom as long, as I can't open dev options. This will get a bigger operation. But maybe I will return to dalvik anyway as I can't see a really convincing advantage in using ART.
Click to expand...
Click to collapse
It just crossed my mind that the theory that ART broke dev options is correct. You COULD.enter dev options initially because you couldn't switch to ART in the first place. And after switching dev options didn't work.... Right? There is no ROM that has ART enabled by default.
Ok, if you don't want to full wipe and start over, here's a quick workaround to get you back to Dalvik. Install Xposed framework and reboot after activating it. Xposed is not ART compatible and has a safety measure built in...whenever try to install it, it switches to Dalvik automatically
Sent from nowhere over the air..
EDIT: It's a little bit unclear for me how the "multi window" feature work. There's a note in the Halo settings screen that if Halo is enabled, multi window is disabled. OK, I've disabled Halo completely, now what? There's no option I can see to make the apps show in multi window. Is there something that should be done?
Found a strange "bug" if I may call it like this but it's annoying as hell. I text alot. Mostly on whatsapp and I am using SwiftKey keyboard that's one of the best. Well, I am used to type fast, I swipe alot and I can say I am pretty good at it. What I've noticed though since I used this ROM, is that I have a lot of cases in which I don't insert "space" between words even if I was sure I've pressed space. Then I start to pay attention to this detail and I've noticed that there a small bottom area, several millimeters tall that's unresponsive some times. Not all the times, just sometimes. If I press any keyboard button on the bottom row like space, punctuation and so on, nothing happens. On a second tap it start to react but if I send the message and start another one it happens again. The area is almost half the height of the space bar and therefore it's happening not to insert a space. I've tested this alot till I figured it out. Don't know why is happening but it's present only on this ROM. I type the same every time and I am not talking about just few words. I've flashed and used this ROM since it was released so I was texting alot whole day. Now I've switched to Beanstalk and it's not happening. Don't know how to isolate the issue or if it was only for me but I thought it worth to be mentioned
Multi window is on as long as halo isn't activated there are no options for multi window just turn halo off then in your recent apps just long press an app and choose multi window