http://teamdirt.me/showthread.php?103-ROM-16-10-12-Cyanogen-9-GSM
-------------------------
Cant wait for this man! Thanks for your work and not just kanging everything:good::victory: (i think we all know who i'm referring to =P)
whaatttttttt
one more issue oh ****k
wt hapnd?
a true lfc supporter
and a former symbian lover
sent from my awesome HTC One V using xda premium
SUPPORT THE SOFTWARE DEVELOPER'S IF YOU LIKE THE GAME / APP BUY IT
Lloir said:
i need testers please....i just finished
this is the download i need testing
i was going to do it myself...but yea....and for the love of god dont flash the boot.img in the zip just make sure you have titanium kernel... not the KISS kernel.
when your device is just coming out of recovery run this adb command
adb logcat > logcat.txt
send me the logcat please!
thanks
Click to expand...
Click to collapse
so, the kiss kernel has bricked your one v? the rom itself is safe right? answer me and i'll get you logcats
1ceb0x said:
so, the kiss kernel has bricked your one v?
Click to expand...
Click to collapse
Cant imagine that. I flash my kernel builds and use
it with myONE now for a long time
The boot.img contents are 1:1 as Titanium just zImage
and modules are different
@Llior:
If you need any additional things in the kernel just tell me
Regards
max
also 8 people downloaded...i have gotten ONE logcat...... i also need a logcat of the booted rom goto settings > developer doodah > usb debugging on
the phone actually boots, the logcat is attached.
some bugs I noticed so far:
some sort of mouse on the touchscreen
adb stops working after boot
system-ui and trebuchet are crashing directly after boot
adb doesn't work on second boot, too
can't go to settings -> usb-debugging =/
TechnoLover said:
the phone actually boots, the logcat is attached.
some bugs I noticed so far:
some sort of mouse on the touchscreen
adb stops working after boot
system-ui and trebuchet are crashing directly after boot
adb doesn't work on after first boot
Click to expand...
Click to collapse
great -.- i thought i had fixed them.....the mouse thing is just the debug touchscreen, im not overly concerned about that....what im going to do is put this on hold again until my phone is repaired
Lloir said:
great -.- i thought i had fixed them.....the mouse thing is just the debug touchscreen, im not overly concerned about that....what im going to do is put this on hold again until my phone is repaired
Click to expand...
Click to collapse
lloir, I maybe can help you with development until your phone gets repaired. is wifi fixed or we can't even reach there?
looking at the logcat already, i can see that camera is not fixed (i know this wasn't in the works in this time), we also miss some .jar framework files - well maybe not miss them but the dalvikvm sure wants them -
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.htc.android.bluetooth.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/wimax.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/usbnet.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.orange.authentication.simcard.jar'
this error appears several times;
also my guess is that there is no statusbar (systemui.apk must be corrupted - trying to take one from another cm9 - maybe saga one?):
W/StatusBarManager( 1802): warning: no STATUS_BAR_SERVICE
missing libraries:
E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser.so' not found
E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LITE_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser_lite.so' not found
it also seems that wifi is fixed (until we can enable it and see if the drivers really works):
I/SystemServer( 1802): Connectivity Service
I/WifiService( 1802): WifiService starting up with Wi-Fi disabled
All in all, our really problem is that the dalvikvm is trying to decompile some frameworks that are missing, and they are this ones, reported earlier:
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.htc.android.bluetooth.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/wimax.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/usbnet.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.orange.authentication.simcard.jar'
1ceb0x said:
lloir, I maybe can help you with development until your phone gets repaired. is wifi fixed or we can't even reach there?
looking at the logcat already, i can see that camera is not fixed (i know this wasn't in the works in this time), we also miss some .jar framework files - well maybe not miss them but the dalvikvm sure wants them -
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.htc.android.bluetooth.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/wimax.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/usbnet.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.orange.authentication.simcard.jar'
this error appears several times;
also my guess is that there is no statusbar (systemui.apk must be corrupted - trying to take one from another cm9 - maybe saga one?):
W/StatusBarManager( 1802): warning: no STATUS_BAR_SERVICE
missing libraries:
E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser.so' not found
E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LITE_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser_lite.so' not found
it also seems that wifi is fixed (until we can enable it and see if the drivers really works):
I/SystemServer( 1802): Connectivity Service
I/WifiService( 1802): WifiService starting up with Wi-Fi disabled
All in all, our really problem is that the dalvikvm is trying to decompile some frameworks that are missing, and they are this ones, reported earlier:
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.htc.android.bluetooth.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/wimax.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/usbnet.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.orange.authentication.simcard.jar'
Click to expand...
Click to collapse
thats init.rc side which is what i edited when my phone died....but those are just meaningless errors
edit i didnt notice E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser.so' not found
E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LITE_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser_lite.so' not found
before.. also all the people that have asked me for the device tree....it's heavily modified and only i myself know whats what in it at the moment....so i would rather not give anyone the device tree
sorry
1ceb0x said:
I'm not requiring anything. Just trying to fix those errors in your rom that i've downloaded If some progress will be made, I'll PM you!
Click to expand...
Click to collapse
ok you need to sort out the main error, the apk's crashing on boot......i have a second .zip i want to test...i'll pm you the link..
Lloir said:
Test build #1
YOU FLASH THIS BUILD AT YOUR OWN RISK
what SHOULD be working in this build:
the debugging cursor should be gone and sound should be working also all the forcecloses should be dead too...
bare in mind I CANNOT test these builds...i NEED logcats from boot and a 2nd logcat after everything has loaded
the 2nd logcat is the most important one right now...logcat NEEDS to be running when you activate wifi\bluetooth AND gps
camera is for when everything else is fixed.
Click to expand...
Click to collapse
i'll rush home and will talk to you on gtalk.
hopefully wifi/bluetooth and gps are fixed so we can enjoy cm9.
1ceb0x said:
i'll rush home and will talk to you on gtalk.
hopefully wifi/bluetooth and gps are fixed so we can enjoy cm9.
Click to expand...
Click to collapse
i wish..... the LEAST i want to get fixed right now is Sdcard and wifi if i can get these fixed before i get my device back (around 7days from tomorrow) then i'll be happy...
i also need people to activate usb storage when logcat is running
im just hoping this build ACTUALLY boots getting annoyed about my ONE V and the corrupt blocks
Lloir said:
i also need people to activate usb storage when logcat is running
im just hoping this build ACTUALLY boots getting annoyed about my ONE V and the corrupt blocks
Click to expand...
Click to collapse
don't worry, i'll cover all the parts. this is the same build you've sent me in PM?
1ceb0x said:
don't worry, i'll cover all the parts. this is the same build you've sent me in PM?
Click to expand...
Click to collapse
yeap, this is the compiled version
Hello people,
Yes, the download was removed because we are working on fixing the issues.
Yesterday we fixed the black screen and launcher crash at startup and we have visual contact with the homescreen. We can flinger the screen and see how it moves, bud sadly there is something wrong because almost all apps are crashing when accessing them. But at least we can boot up fine and see how it looks.
It looks super nice, it is stock cm9, if anyone wants screens you can search everywhere on the internet, I am sure you will find videos and screens, because I have removed it and restored my nandroid because there is nothing I can do with the rom.
We will continue working on it, I'm testing the builds for Lloir and providing him with logcats about the issues.
Right now I sent him various logcats and I expect to speak with him over this weekend about another baked rom but it will not be released until we fix the issues we have now.
I have one screenshot that I forgot i took it yesterday to test the screenshot feature, it doesn't has wallpaper because as default we have a livewallpaper set and i removed it, so the screen will be black but you can still see the statusbar and the dockbar..
{
"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"
}
Regards,
Dragos
i wont be doing any builds until sunday\monday im working saturday night and probably sleeping most of sunday...and today i need to spend time with gf and rebuild linux kernel (not for android)
i've had sometime to think about this....and i have decided i want to get CM9 out ASAP....so i've decided i will let a couple of people who must be able to do the following:
Able to use GIT PUSH\PULL
Able to compile from source
Able to read\understand logcats
Put up with the way i've got the device tree
also understand that myself and Sandvold still get the final say if anyone wishes to use this source to make they're own Rom
i dont want to hold anyone's hand through this.... so PM me your github name and i will let you on as a collaborator.
btw this is setup for GSM at the moment....CM9 CDMA has more problems than this
thanks
-Lloir
Related
6/26-Added earlier themed verions
Well, by now I know that most have seen either my earlier versions or iterations thereof that have been done by several other members. It's been extremely flattering to receive so many compliments and requests for use...Thank you!
Here's my newest edition. It's still blue, but the hues have been tweaked a bit, and I think I've got it pretty nice for the SGS2.
Screenshots courtesy of esk02k. Thank you! Also, thanks to fernando sor, from the evo and dinc forum's....he found a slightly different manifest that lets me theme the comments page properly
{
"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"
}
And here's one showing the widget:
FLASH IN RECOVERY
Market2.3.6-TransBlue_v2.2.3BT.zip
SPECIAL NOTES
*You must not have a com.android.vending in /data/app* I just looked and KE7 ships with Vending 2.3.4 so you likely have received a silent update to 2.3.6. Market updates are installed as /data/app/com.android.vending-1.apk. If you notice that nothing has changed after you flash my zip, go to settings>applications>manage applications, then under the all tab scroll to Market and uninstall updates.
*IF THE MARKET FC'S*
With a root explorer, mount system and delete these:
/system/app/Vending.apk
/data/dalvik-cache/[email protected]@[email protected]
In terminal emulator (press enter/return after each line)
Code:
su
pm uninstall com.android.vending
Reboot phone once normally, then reboot to recovery and reflash zip.
*NOTE: using this method will break any Market shortcuts you have on different pages. You will have to add the shortcuts back again. The main app launcher in your drawer however is fine.
Click to expand...
Click to collapse
If you are new
Often times I forget that there are some reading this that don't really know much and are just getting their feet wet. Here are some general guidelines for my threads (and most threads in general).
You are responsible for your own device. Lots of help around if you get into trouble, though.
Have a backup-This is said so often it really shouldn't need to be said no matter how new you are. This is a bleeding edge hobbiest/development community (dare I say the premier development community), and as such most information should be considered experimental. There is always the possibility that a mod/file/script could mess things up. Occasionally, there may even be a file that you download from a well intentioned dev that had an unknown bug that you 'helped' discover. Make sure you have a backup plan in place before you modify your device. You don't necessarily have to perform a full nandroid backup before each flash, but you should at least have a nandroid that's recent enough that if you did have to use it, it's not the end of the world.
If you're unsure-please ask FIRST. Either in the thread or if you're uncomfortable with public posts, then please pm me. I usually will answer a pm within 24hrs or less. And ask anyone who's pm'ed me for help, I'm very, very thorough
Thanks everyone for your support, and a very special THANK YOU to those who've passed me a drink or two
OTHER THEME EDITIONS
These are the same Market version, but prior theme versions.
4/16
TransBlue_v2.1_Market-2.3.6.zip
TransRed_v2.1_Market-2.3.6.zip
TransGreen_v2.1-Market2.3.6.zip
If you feel inclined please use either the "Thanks" button below, or the "special" thanks button right above my avatar
Thanks everyone for your comments and a special thanks to those who've passed me a drink or two
Click to expand...
Click to collapse
Change Log/Notes
6/18
Most of the major changes are in the details with this release. Some may not be aware of this, but most (maybe all) apk's don't contain 100% of the resources used in the app. There are several drawable's that most apps use that are public resources from the rom itself. Things like buttons, checkbox's, dropbox's, progressbar's, etc. Certainly efficient, but this can be cause for some elements of a themed app to look out of place. (unless it's part of an entire themed rom) That is what I mainly worked on with this version......preventing the use of public resources and forcing my own that I have added. The goal being to have this look the exact same on every device, no matter what theme the rom may or may not have.
This has been quite a time consuming process for me as I experiment with different techniques, and consequently is still a bit of a work in progress. So if you really explore some of the less traveled areas of the apk, you'll likely find a few items I've missed. Please let me know about them
6/21
Many are having issues with fc's, as a result of the edited AndroidManifest but not all. It is breaking permissions with GoogleServicesFramework. I'm hopeful that I can resolve the error, but with my work schedule and taking summer classes I'm just very stretched for time. So for those who did have fc's with either version, please download the alternate versions labeled with "og_manifest" They use the stock manifest file which means I lose the transparent background for the comments page, but that's it. All of the other new mods are still intact and working just fine.
6/26
After a lot of troubleshooting as well as experimentation, all problems seem to be gone. Have had zero issues for a few days now, as well as other reports indicating the same. So the new apk is FULLY transparent, meaning that ALL page views support a transparent window now. I added one more new tweak and that's a new progressbar_indeterminate. This is another custom graphic that I actually just made yesterday, hope you like it! Here's a little sample gif I made of it:
i am going to try this
Very nice job !
I've just tried two times to install with recovery with the first one but nothing have changed... I have still the usual market...
I'm on lightening kf1.
edit/ it say installed...I can see your logo but when I reboot nothing have changed.
syps54 said:
Very nice job !
I've just tried two times to install with recovery with the first one but nothing have changed... I have still the usual market...
I'm on lightening kf1.
edit/ it say installed...I can see your logo but when I reboot nothing have changed.
Click to expand...
Click to collapse
Same here, I can't get it to work (Litening 1.4/KF1)
syps54 said:
Very nice job !
I've just tried two times to install with recovery with the first one but nothing have changed... I have still the usual market...
I'm on lightening kf1.
edit/ it say installed...I can see your logo but when I reboot nothing have changed.
Click to expand...
Click to collapse
OK, this could be from one of two things. First, try the easy fix and go to settings>applications>managage applications and select the all tab. Scroll down to Market, and if there's an option to uninstall updates select that. That should remove any entry in /data/app if you have one (it would be /data/app/com.android.vending-1.apk)
If that's not an option, then it could be an incompatibility with my mount command. I have confirmed reports of it taking just fine with 4.0.0.2 as well as 3.0.0.5. But I also have a report of it not taking with CF's kernel....
Just edited the op to reflect this, but I checked the KE7 firmware I have on hand and it did indeed ship with an earlier version of Vending, so many of you likely have a Vending.apk in /system/app, as well as an update /data/app/com.android.vending-1.apk. There can't be any versions in /data or it will take precedence over my themed version.
If you have any problem market not running or similar problems after CWM install.
Remove Market apk file or files completely from:
- /data/app file called com.android.vending-1.apk if there and
- from /system/app Vending.apk with Root Explorer or Super Manager.
Reboot to recovery and wipe (clear) dalvik-cache. After you deleted and clear dalvik-cache let phone boot (it'll take a bit longer since it rebuilds dalvik). Next step is to extract Vending.apk from zip file and copy it in /system/app folder. Again reboot to recovery and wipe dalvik-cache. If some trouble with file set right premissions like in picture (644); >> in Root Explorer long press on apk file and it will open menu and from menu select Premission or similar below (thanks to corgar for picture). Reboot and everything should work.
damned ! fc now need to reflash thx u dude !
djase said:
damned ! fc now need to reflash thx u dude !
Click to expand...
Click to collapse
Mine fc'ed too, but after I placed com.android.vending-1.apk back in /data/app it worked again. So no re-flash necesary.
TvBTvB said:
Mine fc'ed too, but after I placed com.android.vending-1.apk back in /data/app it worked again. So no re-flash necesary.
Click to expand...
Click to collapse
can u upload please ?
cheers
djase said:
can u upload please ?
cheers
Click to expand...
Click to collapse
Sure, but I'm not sure if my file will work on your phone.
it works thx TvBTvB !
you saved my day !
cheers
You may have to go into manage applications and then uninstall updates from market.
That's what I had to do or it would stay green.
Looks nice ! Not work on Litening Rom 1.4 KF1.I have FC.I wait for a working update
Maybe save the original files to a folder then moved the modded ones with root explorer ....probably a safer way if it doesn't work ...
djase said:
damned ! fc now need to reflash thx u dude !
Click to expand...
Click to collapse
Easy there fella, no need for the "thanks dude"....
Now that I've said that, did you happen to get a logcat of your fc? In pretty much all cases I've been able to help folks who have had an issue with a themed market (mine or others). I've had thousands of downloads since I started theming the Market last November. Really not bragging or anything but I'm just sayin....that I *might* be able to help.
TvBTvB said:
Mine fc'ed too, but after I placed com.android.vending-1.apk back in /data/app it worked again. So no re-flash necesary.
Click to expand...
Click to collapse
Again, did you happen to check logcat? I'm not a logcat expert, but it usually helps. As far as reflashing, this kind of "flashing" is very basic. Really all that it's doing is pushing. You'd achieve the exact same result by using adb push while in recovery (or even just by stopping core)
pendo said:
Again, did you happen to check logcat? I'm not a logcat expert, but it usually helps. As far as reflashing, this kind of "flashing" is very basic. Really all that it's doing is pushing. You'd achieve the exact same result by using adb push while in recovery (or even just by stopping core)
Click to expand...
Click to collapse
I was finally able to reproduce the problem, here is the logcat:
Code:
I/ActivityThread( 5817): Pub com.android.vending.SuggestionsProvider: com.android.vending.SuggestionsProvider
D/vending ( 5817): [1] VendingApplication.onCreate(): Resetting ServiceLocator from app
D/dalvikvm( 5817): GC_CONCURRENT freed 205K, 50% free 2822K/5639K, external 0K/0K, paused 1ms+2ms
D/dalvikvm( 5817): GC_EXTERNAL_ALLOC freed 1K, 50% free 2820K/5639K, external 0K/0K, paused 26ms
D/dalvikvm( 5817): GC_CONCURRENT freed 21K, 45% free 3327K/5959K, external 8K/514K, paused 1ms+3ms
D/dalvikvm( 5817): GC_EXTERNAL_ALLOC freed 524K, 51% free 3101K/6279K, external 375K/514K, paused 23ms
D/dalvikvm( 5742): GC_CONCURRENT freed 468K, 57% free 2930K/6791K, external 435K/776K, paused 2ms+2ms
D/ResourceType( 5817): calling getConfigurations
D/ResourceType( 5817): called getConfigurations size=219
D/CLIPBOARD( 5742): Hide Clipboard dialog at Starting input: finished by someone else... !
D/dalvikvm( 5817): GC_CONCURRENT freed 96K, 42% free 3766K/6471K, external 609K/781K, paused 1ms+2ms
D/CLIPBOARD( 5817): Hide Clipboard dialog at Starting input: finished by someone else... !
D/dalvikvm( 5817): GC_CONCURRENT freed 700K, 47% free 3738K/7047K, external 609K/781K, paused 1ms+2ms
I/ActivityManager( 2908): Displayed com.android.vending/.AssetBrowserActivity: +738ms
D/alogcat ( 5742): stopping ...
D/alogcat ( 5742): stopped
D/dalvikvm( 5817): GC_FOR_MALLOC freed 407K, 51% free 3466K/7047K, external 609K/781K, paused 17ms
D/dalvikvm( 5817): GC_CONCURRENT freed 283K, 49% free 3662K/7047K, external 632K/781K, paused 1ms+2ms
E/DatabaseUtils( 3415): Writing exception to parcel
E/DatabaseUtils( 3415): java.lang.SecurityException: Permission Denial: writing com.google.android.gsf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=5817, uid=10012 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS
E/DatabaseUtils( 3415): at android.content.ContentProvider$Transport.enforceWritePermission(ContentProvider.java:361)
E/DatabaseUtils( 3415): at android.content.ContentProvider$Transport.insert(ContentProvider.java:197)
E/DatabaseUtils( 3415): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:146)
E/DatabaseUtils( 3415): at android.os.Binder.execTransact(Binder.java:320)
E/DatabaseUtils( 3415): at dalvik.system.NativeStart.run(Native Method)
W/dalvikvm( 5817): threadid=11: thread exiting with uncaught exception (group=0x4001e578)
E/ ( 2908): Dumpstate > /data/log/dumpstate_app_error
I/dumpstate( 5855): begin
D/dalvikvm( 5817): GC_EXTERNAL_ALLOC freed 399K, 49% free 3628K/7047K, external 755K/781K, paused 27ms
D/dalvikvm( 5817): GC_EXTERNAL_ALLOC freed 5K, 49% free 3627K/7047K, external 1287K/1296K, paused 24ms
E/lights ( 2908): write_int: path /sys/devices/virtual/misc/melfas_touchkey/brightness, value 2
I/dumpstate( 5855): done
TvBTvB said:
I was finally able to reproduce the problem, here is the logcat:
Click to expand...
Click to collapse
Thank you. The AndroidManifest that I introduced in this revision seems to be the instigating the fc. But it's different than when I've experimented with changing the manifest in months past, as I (and many others) have it runnning fine. However, while updating an app earlier, I too had the fc.
I am updating the op with additional versions that have "og_manifest" at the end of their file names. The one thing that I give up with this is that the comments page will revert to a white background. But it is 100% stable, for sure.
pendo said:
Thank you. The AndroidManifest that I introduced in this revision seems to be the instigating the fc. But it's different than when I've experimented with changing the manifest in months past, as I (and many others) have it runnning fine. However, while updating an app earlier, I too had the fc.
I am updating the op with additional versions that have "og_manifest" at the end of their file names. The one thing that I give up with this is that the comments page will revert to a white background. But it is 100% stable, for sure.
Click to expand...
Click to collapse
Its strange that some people get fc with these, ive never had the problem on multiple phones and multiple roms. Just flashed villain rom yesterday and i can confirm that the market works perfectly, the new manifest one with the transparent comments page. Your market was the first thing i flashed actually, before even adding my own mods. It must be something to do with what the ROM chefs are doing to there ROMS. Fix something here, break something there lol.
This is based on the latest stable release 7.2 from Cyanogen.
This is a personal build and is my first attempt at customising CM.
{
"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"
}
Apks removed:
ADWLauncher
Androidian
Browser
CMStats
CMUpdateNotify
CMWallpapers
Cyanbread
Development
FileExplorer
Gallery3D
Music
Pacman
ProTips
QuickSearchBox
Click to expand...
Click to collapse
Apps Added:
AdAway
AdobeFlashPlayer
AdobeReader
BoatBrowser
Facebook
FasterGPS
GestureSearch
Google+
GoogleMaps
LauncherPro
PlayMusic
Pocket
QuickPic
SMS Backup & Restore
SolidExplorer
Talk2
TitaniumBackup
Twitter
WhatsApp
XDA
YouTube
Click to expand...
Click to collapse
Other Changes:
Included Updated Gapps
Elite Kernel by nik3r
Virtuous OC Daemon by virtuous
Zipaligned
EXT4 optimisation
Wipe EFS on flashing
Radio libs for 04.19
V6Supercharger U9RC8.2 Script extracted to sdcard
Busybox 1.20
Build prop tweaks
Debugging notification disabled
Default theme changed
Ringtones,Notifications sounds from HTC and MIUI included.
Bootanimation changed
LauncherPro icons changed
Click to expand...
Click to collapse
Instructions:
Full Wipe necessary(Superwipe)
First boot after install will be very slow. After it boots wait for some time or force close launcher pro. Also you may have to force close launcherpro after every reboot. UI might be slow after that which can be fixed inside launcher pro advanced settings
Play Store(if not present) will show up after adding your Google account in the settings menu.
Click to expand...
Click to collapse
Downloads:
Strawmetal.CM.V6
Strawmetal.CM.V5, MD5 = 689cf8f5aca476dd766bdaed60e7f61c
Strawmetal.CM.V4, MD5 = acb53c252dd66ca91cb8cb992e50a6ad
Strawmetal.CM.V3
Strawmetal.CM.V2
Click to expand...
Click to collapse
Hmmm. ROM looks very interesting
Test Time.
Downloading.
THX
zibiss said:
Hmmm. ROM looks very interesting
Test Time.
Downloading.
THX
Click to expand...
Click to collapse
<3 Strawmetal sauce. Is this a Sony theme? I love it!
---------- Post added at 01:10 AM ---------- Previous post was at 12:35 AM ----------
Getting a frozen white HTC screen with this:
Code:
I/AudioHardwareMSM7X30( 1513): Setting in-call volume to 100 (available range is
0 to 100)
E/AudioHardwareMSM7X30( 1513): msm_set_voice_rx_vol(100) failed errno = 1
Looks very well! Indeed nicely themed! Gonna try it out when I have the time
Quote nice this rom. Unfortunately, the airbnb search function is causing a force close. Can anyone else confirm? Or know why?
Sent from my HTC Vision using XDA
Ok, so it looks like I will download this... again!
Edit: Now I get a bootloop.
Bootloops.
logcat says this:
Code:
E/HTC Acoustic( 1493): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 1493): failed to open A2051 CSV files /system/etc/TPA2051_CFG.csv.
E/AudioHardwareMSM7X30( 1493): msm_set_voice_rx_vol(100) failed errno = 1
E/AndroidRuntime( 1507): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
E/AndroidRuntime( 1507): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 1507): at com.android.server.ServerThread.run(SystemServer.java:170)
E/AndroidRuntime( 1507): Caused by: java.lang.NumberFormatException: unable to parse '' as integer
E/AndroidRuntime( 1507): at java.lang.Integer.parseInt(Integer.java:362)
E/AndroidRuntime( 1507): at java.lang.Integer.parseInt(Integer.java:332)
E/AndroidRuntime( 1507): at java.lang.Integer.valueOf(Integer.java:506)
E/AndroidRuntime( 1507): at com.android.server.am.ActivityManagerService.getIntProp(ActivityManagerService.java:356)
E/AndroidRuntime( 1507): at com.android.server.am.ActivityManagerService.
<clinit>(ActivityManagerService.java:365)
E/AndroidRuntime( 1507): ... 1 more
E/AndroidRuntime( 1507): Error reporting crash
E/AndroidRuntime( 1507): java.lang.NullPointerException
E/AndroidRuntime( 1507): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 1507): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:854)
E/AndroidRuntime( 1507): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:851)
See, I'm wondering if the people who got it to work just flashed V2 over V1? Anyone who got it to work without having V1 installed first?
Edit: 4th download, using Chrome, Orbit downloader, and IE8/9. No difference.
nickeedoo said:
See, I'm wondering if the people who got it to work just flashed V2 over V1? Anyone who got it to work without having V1 installed first?
Edit: 4th download, using Chrome, Orbit downloader, and IE8/9. No difference.
Click to expand...
Click to collapse
I flashed V2 after superwipe and no issues at all... but i'll verify it a few more times and report....
EDIT: I took the screenshots on V2...(so it didnt bootloop for me)
EDIT: Made a superwipe again and it boots again without issues...I'll reupload the rom again... please look for it tomorrow at the latest...md5 will be posted
Hmm... try reuploading? Or making an md5? I did that on all the files I downloaded and they're the same every time.
Am I the only one who had a successful install of this rom? I came from ILWT, flashed data / cache then did superwipe+ext4 then wipe dalvik. It actually booted quite fast, In under 20-30 seconds it seemed.
Upon boot, the rom ran very smooth and quick. My only complaint was airbnb wasn't working, which it was working on ILWT, so I had to go back to ILWT. Shame because I really like this rom. Aside from the theme which I got bored of quickly. Thanks for the upload!! Good work.
Sent from my HTC Vision using XDA
Apparently, you must use superwipe before installing this rom. Simply going to "format all (except SD)" doesn't seem to work. Thanks! I'll test this right away!
Edit:
.... RAGE MODE ACTIVATED!! Adb says the following services died:
sensorservice
entropy
power
media.audioflinger
media.player
media.camera
media.audio_policy.
I see this line:
"Failed to open A2051 CSV files /system/etc/TPA2051_CFG.v"
Edit2: It works!
V3 Testing
V3 out for testing.
Changelog:
Included NeverGone\RU's earphone volume mod
Updated market apps
Bootanimation disabled for faster booting.
Instructions:
Wipe cache,dalvik if updating from V2
Full Superwipe necessary if flashing over any other rom...
REQUEST:
Please test if the volume mod is working and report any issues.
What is airbnb????
Will update this link into OP after you guys say its okay
strawmetal said:
V3 out for testing.
Changelog:
Included NeverGone\RU's earphone volume mod
Updated market apps
Bootanimation disabled for faster booting.
Instructions:
Wipe cache,dalvik if updating from V2
Full Superwipe necessary if flashing over any other rom...
REQUEST:
Please test if the volume mod is working and report any issues.
What is airbnb????
Will update this link into OP after you guys say its okay
Click to expand...
Click to collapse
Airbnb is just an app I use to search vacation properties when I go on vacation. But I use it often and it wasn't working. So I had to change roms. Not sure why it wasn't working. I'm back on ILWT and it's working fine again.
Sent from my HTC Vision using XDA
For some reason on minus its showing me that the file doesn't exit really want to try this out, I logged in and still no good. Hmm.
Sent from my HTC Vision using xda premium
mrbmg said:
For some reason on minus its showing me that the file doesn't exit really want to try this out, I logged in and still no good. Hmm.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
That's too bad, this rom is awesome! Minus worked for me using dolphin hd.
Sent from my HTC Vision using XDA
strawmetal said:
V3 out for testing.
...
Click to expand...
Click to collapse
Thanks! I couldn't get v2 to boot so will try this one tonight when I have some time to do so
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
Palingenesis said:
That's too bad, this rom is awesome! Minus worked for me using dolphin hd.
Sent from my HTC Vision using XDA
Click to expand...
Click to collapse
If you download with your phone sometimes it works to go to the normal page instead of mobile page.
Why is this downloading at 27 kb/s :| Lolololol
Again I cannot get it to boot, i have made a logcat, maybe this helps http://pastebin.com/5RYq648A I did a superwipe before installing.
Hagelslagje said:
Again I cannot get it to boot, i have made a logcat, maybe this helps http://pastebin.com/5RYq648A I did a superwipe before installing.
Click to expand...
Click to collapse
Sorry to hear that you guys aren't able to boot it .... Worked flawlessly for me V3 bootup was 14seconds on first flash... .... Anyways i'll build it from scratch again and see if that'll work for you.... Give me a day to do it because i just reverted to stock with no root(am making a sense version)...
Cheers...
{
"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 am going to fill this op with Questions and answers from all devices supported by Team Horizon. Please keep the respect and KEEP ALL NON DEVELOPMENT DISCUSSION HERE OR OUR
GOOGLE PLUS PAGE
Click to expand...
Click to collapse
.
Click to expand...
Click to collapse
Q. I came from 4.1.2 and I flashed your 4.2.1 and I can't access my files now?
A. Well this is because after the 4.2.1 update Google implemented a feature with in its ROM to allow for the use to apply user specific accounts. I suggest reflashing a 4.1.2 ROM, Then mount the phone once booted, Take all of the information you choose to keep and place it on your desktop, Once complete then reboot the phone into recovery and wipe the rm and reflash 4.2.1 once you have flashed rom and gapps, Before you leave recovery wipe the sd card. Once phone reboots then simply replace the information you placed on your desktop to its corresponding folder.
Click to expand...
Click to collapse
Q. my wifi is always on when in standby?
A.Disable wifi optimization, And avoid poor connections in wifi advanced options.. If you have Franco kernel, wifi fast pm helps too
Click to expand...
Click to collapse
Q. HELP I don't have a rom on my SD card and I am stuck in a boot loop what do I do?
A. You need to make sure you have a working adb setup along with all proper fastboot and device drivers installed. Place the rom you wish to flash in the root of the adb folder.
Make sure phone is in recovery mode and that it is plugged into the computer.
Open a command prompt and cd to the directory of the adb folder. ( or simply hold the shift key and right click your adb folder and choose to open command windows here)
now type: adb push (rom.zip) /sdcard/ (replace the (rom.zip) with the entire name of the rom.zip.)
Click to expand...
Click to collapse
Q. How come fast charge is not working or its enabled but not working?
A. Answer is simple, The roms stock kernel doesn't allow for fast charge. you may simply flash Franco kernel and or any other 4.2.1 kernel that supports to to gain functionality.
Click to expand...
Click to collapse
Q. Can I dirty flash (flash ROM without wipe)?
A Yes you may flash the ROM without wiping. YOU WILL HAVE TO REFLASH GAPPS. We don't recommend doing this but if you are pressed for time or its just too difficult then have at it. We will not support complaints from those that choose to go this route.
Click to expand...
Click to collapse
Warez Removed
Q. I have downloaded the ROM but it wont boot?
A. Please make sure you are downloading the correct ROM and completely wiping before flashing!
Crespo- http://d-h.st/users/iceandfire/?fld_id=9532#files
Grouper- http://d-h.st/users/iceandfire/?fld_id=8701#files
Maguro- http://d-h.st/users/iceandfire/?fld_id=8699#files
Mako- http://d-h.st/users/iceandfire/?fld_id=9438#files
Toro- http://d-h.st/users/iceandfire/?fld_id=8700#files
Toro Plus- http://d-h.st/users/iceandfire/?fld_id=9002#files
Click to expand...
Click to collapse
Q. Somebody know, how to disable waking up phone by pressing volume button?I dont like this feature.
A. Menu>settings>display>enable then disable the volume key MOD
Click to expand...
Click to collapse
Q. Where are my Chrono settings for weather and clock?
A. Menu>System Settings>Display>Clock widget
Click to expand...
Click to collapse
Q. Are the round widgets shown in the OP contained in the ROM? If not, are they available anywhere? Also, I cannot for the life of me figure out how to put a lockscreen widget. When I go into the Chronus settings, there are settings for the clock, weather and calendar widgets, but I can only add the clock widget to my device.
A. OK the widget is not included but called one more clock widget. To apply the clock. Lock the screen then place your finger on the clock and slide down till you reach the lock icon or the white outline is the write screen amd let go. Then long press the clock ad delete it. Then click the add widget . After you enabled everything in display then go to chrono in the options onthe lockscreen (the + sign from earlier) and add it. To add muliple widgets then slide down on clock to fill screen then swipe left or right.
Click to expand...
Click to collapse
Q. What is fast charge? what does it do for me? How do I get it to work?
A.
Fast charge is a option baked into the kernel that doesn't allow the phone to be mounted to the pc.
Keeps computer from mounting your sd card everytime its plugged in.
You need to install a kernel that supports it. Stock XennonHD doesn't allow for this. I suggest using Franco Kernel. found here: http://forum.xda-developers.com/showthread.php?t=1367341
Click to expand...
Click to collapse
Q. What gapps do i install on this rom? I installed the gapps from ice not all my apps are there?
A.
Download these gapps: http://goo.im/gapps/gapps-jb-20121212-signed.zip
Because all of the apps missing can be manually installed from the market. He did this to lighten the download.
Click to expand...
Click to collapse
Q. How to create a log cat
A. the code for logcat to output to a file is
adb logcat > name of problem.txt
you can also do
Click to expand...
Click to collapse
adb logcat -f name of problem.txt
how I prefer to do it is this way
Click to expand...
Click to collapse
:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Click to expand...
Click to collapse
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
Click to expand...
Click to collapse
I then could do the following with logcat:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
Click to expand...
Click to collapse
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Click to expand...
Click to collapse
Q. I am in the download section but what rom is for my device?
A.
Crespo- nexus S
Grouper- Nexus 7
Maguro- gsm galaxy nexus t-mobile
Mako- galaxy nexus 4
Toro- Galaxy nexus Verizon Wireless
Toro Plus- sprint galaxy nexus
Click to expand...
Click to collapse
Click to expand...
Click to collapse
==================================================
Important please read
I. Appreciation
There are many ways to show your support to us. You can:
Press the "Thanks" button.
Hit the donation button and help support the team
Wear our specially prepared banner
Share your opinion about my work and write some feedback in our threads.
Advertise our work to your friends, family, anyone who owns this device.
Rate our threads with 5 stars.
We appreciate all the support you give us, but we don't expect anything
Click to expand...
Click to collapse
II. Sharing
XDA-Developers.com is all about sharing. If you would like to use any part of our work, please feel free to do so but remember to do the following beforehand:
Inform - Please send us a PM or email telling us
Permission - Please, if you do not have permission from us, don't use it. Most of the time, we will allow you to, but if you don't get our permission first, we will report.
Credits - No one wants their work stolen. Please remember to give proper credits when using our work.
Click to expand...
Click to collapse
:
III. Support
If you have any issues or questions, please feel free to post them in the our threads. However, because all of us have social lives outside of XDA, your questions may not always be answered right away. Members who are more experienced in our work, please help out the ones who don't.
If you want to get the fastest and the best answer - ask the question in our threads instead of PM'ing us. Chances are, other users will be able to help you when Team Members don't have the time to.
Click to expand...
Click to collapse
IV. Updates
We are a busy team! Every Team Member has lives outside of XDA. You cannot expect us to sit in front of the computer all day and develop Android. Please do not ask for ETA's. The update will come when we release it. Sometimes, there is a good reason for why we have not released an update in a while. Please be patient with us, we will do as we promise. Updates will come.
Click to expand...
Click to collapse
V. Responsibilities
We are not responsible for your device! We do not guarantee that everything will work the way it's supposed to. Not every device is created equal, what might work on our devices may not work on yours or vice versa. Please be a responsible person when it comes to flashing. This is a mature site, don't act immaturely when your device becomes problematic. If you cry and blame us for "destroying" your device, we will laugh at you. Your device is your responsibility, act like it.
Thanks for choosing Team Horizon, we hope you enjoy our works as much as we enjoy working with them.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
MOD Section
This is going to be a section where I post add ons for this ROM. Enjoy!
Click to expand...
Click to collapse
<---------http://dl.dropbox.com/u/44672998/supporter.png
My Dev-Host Account With All The Add On Downloads!
http://goo.gl/4rscI
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Invered Gapps! 4.2.1
CLICK ME
Click to expand...
Click to collapse
:highfive:
HELP!
Please Help Contribute To This Project. Either Post Question With Answer and I Will Add To OP or PM Me The Stoofz
:highfive:
Great idea Tory, You have been a real asset to the team, thanks for all you do.
Sent from my SCH-I535 using Tapatalk 2
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
crispy1 said:
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am on latest franco and fixing to test wifi tether. hold (on gsm tho)
crispy1 said:
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was able to connect wifi tether and usb tether with the latest franco. Keep in mind that I ALWAYS WIPE before flashing any updates to iron out those pesky little bugs.
pr0xy mAn1Ac said:
I was able to connect wifi tether and usb tether with the latest franco. Keep in mind that I ALWAYS WIPE before flashing any updates to iron out those pesky little bugs.
Click to expand...
Click to collapse
OK, good to know. I'll flash Franco and if it is still broken, I'll clean flash 1.5 followed by an update to Franco.
Sent from my Galaxy Nexus using Tapatalk 2
crispy1 said:
OK, good to know. I'll flash Franco and if it is still broken, I'll clean flash 1.5 followed by an update to Franco.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Please keep us posted on your progress. let me know if I can help.
Quick Unlock
Is quick unlock working? It has not worked for me for a while, but I saw one person say it works. I have done a full wipe with each version. Thanks!
pr0xy mAn1Ac said:
Please keep us posted on your progress. let me know if I can help.
Click to expand...
Click to collapse
I reflashed clean and am still unable to connect. Still on default kernel. I can see the network but I cannot connect even without security. Tried both an iPad and an Android tablet. Blue tooth tether works but that us too slow. I'm out of options. This is a show stopper for me.
Sent from my Galaxy Nexus using Tapatalk 2
crispy1 said:
I reflashed clean and am still unable to connect. Still on default kernel. I can see the network but I cannot connect even without security. Tried both an iPad and an Android tablet. Blue tooth tether works but that us too slow. I'm out of options. This is a show stopper for me.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I have to have tethering. Flashed back to CNA 3.8 and I got it back. May need to hang on to 4.1.2 a bit longer.
Sent from my iPad using Tapatalk HD
crispy1 said:
I have to have tethering. Flashed back to CNA 3.8 and I got it back. May need to hang on to 4.1.2 a bit longer.
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
edited
10char
Navigation bar opacity
I love the whole ROM, been using it for a while. I was very excited to see a translucent menu bar option in the 12/30/12 release. However im not sure of its functioning properly. On the home screen the nav bar is translucent however in any app its a solid black background again. When I zoom using accessibility feature (triple tap) the nave bar goes back to being all but invisible. Is this transparent effect only supposed to do what it does on my case? Thanks man, keep up the good work
Just a quick question pr0xy ... Do I have to wipe data in order to install inverted gapps or can i dirty flash over the 20121212 package? Thx in advance!
Just flash the gapps brother no wiping needed. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
Ok, another stupid question inc! :/ Proxy - do you know of any place where I could get "Black Facebook" to match the inverted gapps ? Since I kinda prefer it over the stock white FB app ... I could find only some lower versions which are slow and buggy, so ... Thx in advance
Doomhamma said:
Ok, another stupid question inc! :/ Proxy - do you know of any place where I could get "Black Facebook" to match the inverted gapps ? Since I kinda prefer it over the stock white FB app ... I could find only some lower versions which are slow and buggy, so ... Thx in advance
Click to expand...
Click to collapse
It is included with the inverted gapps. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
pr0xy mAn1Ac said:
It is included with the inverted gapps. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
No it's not ... That's why I asked
*DUMB NEWBIE QUESTION*
how to flash this rom ?
just tried to flash the rom using TWRP, but it stucks at bootlogo.
now restored the rom and N4 is working normal.
any solution ?
thx in advance.
Hey guys i am back with a different UI again and this time LG gets my love. I mean the company and not the girl
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Android 4.1.2 (JZO54K)
NativeSD
Data on ext
LG UI 3.0(partially. I'll theme it more in the next version)
Aroma installer as always
Lg stuff used/ported in this version
Code:
[LIST=1]
[*]LG UI 3.0 launcher
[*]LG UI 3.0 theme
[*]Tried to port LG Camera(I am sure it'll not work but still need someone to prove it wrong)
[*]Some more stuff i don't remember please mention it of you find them
[/LIST]
To-do list
Code:
[LIST=1]
[*]LG optimus G pro lockscreen
[*]Many other LG stuff
Version 1.0
DOWNLOAD
Special thanks to the ever helpful kameirus for beta testing and uploading a mirror
Credits:
Tytung
Xylograph
SecureCRT
Kameirus
wwchang
Robbie.p
And whoever i missed[/B]
Reserved for future versions
Reserved for addons
Reserved for screenshots.someone will need to provide me those
I also tried to port pacman 22.0(android 4.2.2) to hd2
IMPORTANT
Whoever is testing it please leave a reply after you download.and i hope nobody downloads it after that coz i don't want my box account suspended due to heavy traffic as it's the only place i can upload my roms due to my crappy internet
But i couldn't test it.Also kameirus is quite sick(hope he gets well soon) So anyone who is willing to test it, please do it for me but remember it can be tested only on nand only install
This is the rom
https://www.box.com/s/9pnnjbfqxvugbelk85od
While installing choose nand only install to install it. nativesd ramdisk is messed up i guess.if it boots then please check if the basic things work and if there is rom control and pa preferences in settings and then please make a mirror(optional step) and pm me the link
If it doesn't boot then make a logcat while booting and send it to me
After making the logcat replace
The framework folder from the below link in the rom zip
https://www.box.com/s/r7l3dm3hk1q0syl62yht
And again flash the rom. If it boots then please check for the above mentioned things. If it doesn't then please send me a logcat
I'll go to sleep now as it's late here in india
I'll look at your reply in the morning
Sent from my LG-P990 using xda premium
Anurag pandey said:
...
Click to expand...
Click to collapse
Welcome back. It's a long time to see you. Thanks man.
BTW: what is system partition size?
6oltsqs7 said:
Welcome back. It's a long time to see you. Thanks man.
BTW: what is system partition size?
Click to expand...
Click to collapse
Ah i can't see the system partition now.i sold my crappy notebook yesterday . I'll get a new machine by monday to support my development so you'll get to see me a lot around now
Sent from my LG-P990 using xda premium
this is one of the fastest JB i've tried using the default home but stutters when using Xperia home. JB camera is OK but will reboot when using video
others seem to be working ok though I still need to try it out more
thanks for your nice work.
* I tried, but it is not loading android.
Return to WM
mengfei said:
this is one of the fastest JB i've tried using the default home but stutters when using Xperia home. JB camera is OK but will reboot when using video
others seem to be working ok though I still need to try it out more
thanks for your nice work.
Click to expand...
Click to collapse
Thanks for the screenshot buddy.that reminded me of the stuff i forgot about.and this was just a test version.new version will be up by the coming tuesday or Wednesday
Sent from my LG-P990 using xda premium
Why don't use 4.2.2.?
but.. i like 4.1.2 too..
what system partition
abumaha said:
what system partition
Click to expand...
Click to collapse
300mb should be fine
Sent from my LG-P990 using xda premium
Change the date dude, its 25 Apr 13..
Got confused due to the date.
And the link you provided for pacman 4.2.2 ROM doesn't work.
****in bomb update man coooooooool
---------- Post added at 07:18 PM ---------- Previous post was at 07:02 PM ----------
cAMERA NOT WORK DEAR ANY SULOTION
GALERIE NOT WORK
Pacman 4.2.2 doesn't boot as of yet.gets stuck in bootanimation. I got it tested.i will work on fixing it and many more stuff after monday and for the camera, it must work
Thanks for new rom, and welcome back. Hope your exams went well.
Rom looks good. wifi, data BT (a2dp), home and lg launchers all working good. NativeSD
Camcorder gave me
01:15:32.610 Debug QcomCamera 25157 HAL_get_camera_info: loading libcamera at 0x40018414
01:15:32.611 Info MediaRecorderJNI 24985 prepare: surface=0x2a2385d0 (identity=308)
01:15:32.612 Warning StagefrightRecorder 25157 Intended video encoding bit rate (11264000 bps) is too large and will be set to (3000000 bps)
01:15:32.612 Warning StagefrightRecorder 25157 Intended video encoding frame rate (30 fps) is too large and will be set to (15 fps)
01:15:32.613 Warning StagefrightRecorder 25157 Intended video encoding frame width (1280) is too large and will be set to (800)
01:15:32.613 Warning StagefrightRecorder 25157 Intended video encoding frame height (720) is too large and will be set to (480)
01:15:32.614 Debug CameraSource 25157 Camera does not support setVideoSize()
01:15:32.614 Error CameraSource 25157 Video dimension (800x480) is unsupported
01:15:32.615 Error MediaRecorder 24985 start failed: -19
Click to expand...
Click to collapse
When trying to start recording
And then FCs with
Code:
01:25:16.817 Debug AndroidRuntime 24985 Shutting down VM
01:25:16.818 Warning dalvikvm 24985 threadid=1: thread exiting with uncaught exception (group=0x40ab3300)
01:25:16.987 Error AndroidRuntime 24985 FATAL EXCEPTION: main
01:25:16.988 Error AndroidRuntime 24985 java.lang.RuntimeException: getParameters failed (empty parameters)
01:25:16.989 Error AndroidRuntime 24985 at android.hardware.Camera.native_getParameters(Native Method)
01:25:16.989 Error AndroidRuntime 24985 at android.hardware.Camera.getParameters(Camera.java:1539)
01:25:16.990 Error AndroidRuntime 24985 at com.lge.camera.controller.PreviewController.stopPreview(PreviewController.java:604)
01:25:16.991 Error AndroidRuntime 24985 at com.lge.camera.Mediator.onPause(Mediator.java:1519)
01:25:16.992 Error AndroidRuntime 24985 at com.lge.camera.CamcorderMediator.onPause(CamcorderMediator.java:251)
01:25:16.992 Error AndroidRuntime 24985 at com.lge.camera.Camcorder.finish(Camcorder.java:357)
01:25:16.993 Error AndroidRuntime 24985 at android.app.Activity.onBackPressed(Activity.java:2154)
01:25:16.994 Error AndroidRuntime 24985 at android.app.Activity.onKeyUp(Activity.java:2131)
01:25:16.995 Error AndroidRuntime 24985 at com.lge.camera.Camcorder.onKeyUp(Camcorder.java:200)
01:25:16.995 Error AndroidRuntime 24985 at android.view.KeyEvent.dispatch(KeyEvent.java:2655)
01:25:16.996 Error AndroidRuntime 24985 at android.app.Activity.dispatchKeyEvent(Activity.java:2361)
01:25:16.997 Error AndroidRuntime 24985 at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchKeyEvent(PhoneWindow.java:1844)
01:25:16.998 Error AndroidRuntime 24985 at android.view.ViewRootImpl.deliverKeyEventPostIme(ViewRootImpl.java:3577)
01:25:16.998 Error AndroidRuntime 24985 at android.view.ViewRootImpl.handleImeFinishedEvent(ViewRootImpl.java:3547)
01:25:16.999 Error AndroidRuntime 24985 at android.view.ViewRootImpl$ViewRootHandler.handleMessage(ViewRootImpl.java:2797)
01:25:17.000 Error AndroidRuntime 24985 at android.os.Handler.dispatchMessage(Handler.java:99)
01:25:17.000 Error AndroidRuntime 24985 at android.os.Looper.loop(Looper.java:137)
01:25:17.001 Error AndroidRuntime 24985 at android.app.ActivityThread.main(ActivityThread.java:4965)
01:25:17.002 Error AndroidRuntime 24985 at java.lang.reflect.Method.invokeNative(Native Method)
01:25:17.003 Error AndroidRuntime 24985 at java.lang.reflect.Method.invoke(Method.java:511)
01:25:17.003 Error AndroidRuntime 24985 at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
01:25:17.004 Error AndroidRuntime 24985 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
01:25:17.005 Error AndroidRuntime 24985 at dalvik.system.NativeStart.main(Native Method)
01:25:17.006 Warning ActivityManager 281 Force finishing activity com.lge.camera/.Camcorder
Is there a way to set a supported size near to 800x480?
I installed miui camera and camcorder works BTW
Thanks again
Thanks for the log.it was fixed by tytung but i used an old jellybelly base . I'll look at the changes tytung made to make it work
Sent from my LG-P990 using xda premium
to oft reboots
still this rom is not stable enough
would be nice if update coming
soon
why ist his sony ui
i thought lg ui?
anyway fast working rom
{
"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"
}
www.ultrabeamgb-revo.webs.com
UltraBeam REVO
This is UltraBeam REVO V1.7 in it's latest, for now of course. It's based on Cyanogenmod 7.2 nightlies [Latest]. This ROM is here to improve your HTC Wildfire S and has a lot to offer to just one user and to everyone who uses this software. So if you came here to install/test this ROM then please go on.
So then UltraBeam REVO reaches it's stage for theming, and I personally think Holo light blue suits UltraBeam REVO for now...
Theming this ROM was sort of tricky, but it didn't stop me finishing it
There will be varieties of themes in a collection for you to choose. That's after some time.
Features on UltraBeam REVO
Based on CM7.2 nightlies
Play Store 4.3.11 Installed
Very fast and 100% stable
OTA updates, to receive updates
Custom themed [Holo light-blue]
Multitasking ROM, for great use
Viper4Android FX for best music quality
Latest Holo Laucher 2.1.1
Cronmod's Int2ext [Integrated]
Latest Busybox installed
Lastest SU binary 3.1.1 installed
Voice Search Installed
Gallery replaced Quickpic
Init.d tweaks installed
Fly On Mod by Slaid480
http://vipersaudio.com/blog/
Need help?
Thread navigation: 1st post = UltraBeam REVO Downloads, 2nd post = UltraBeam REVO themes, 3rd = UltraBeam REVO Kernels, 4th post = Must Read!
XDA:DevDB Information
UltraBeam REVO, ROM for the HTC Wildfire S
Contributors
Stone. Cold
ROM OS Version: 2.3.x Gingerbread
Based On: AOSP, CyanogenMod
Version Information
Status: Stable
Current Stable Version: 1.7
Stable Release Date: 2014-09-16
Created 2014-09-13
Last Updated 2014-09-16
UltraBeam REVO *Downloads*
UltraBeam REVO
Here's the official UltraBeam REVO system for your device, I'd advise you to head over to the 4th post on how to install this ROM
- REVO V1.7 *Initial release*
UltraBeam REVO *Themes* [Coming Soon]
Reserved for use 2
UltraBeam REVO *Kernels*
Reserved for use 3
READ!
You're using the UltraBeam software, I will advise you to be-careful of making any mistake whilst in the installation section.
If you've successfully installed this software, then please do enjoy it.
Instructions
1. Download the latest UltraBeam REVO V?.?
2. Enter recovery mode on your device and wipe data, cache, dalvik-cache and battery stats
3. Go to mounts & storages and format [System]
WARNING: Never format Boot Partition or you'll end up with a 'Bricked up' device!
4. Switch off your device 'Completely'
5. Reboot back into recovery mode
6. Go to mounts & storages and mount these [System] - [Data]
7. Proceed installation for UltraBeam REVO V?.?
8. After installation process has been completed, you must reboot your device!
9. Once rebooted you may add your Google account VIA settings.
10. Now you must Power off your device 'again'
11. Power back on and enjoy using the UltraBeam REVO system
Once UltraBeam REVO has been safely installed, then please stay up-to-date with our software, to get the latest new features/upgrades to add into the ROM.
Where is the DL link "CAN`T WAIT TO GET SOME"
retryer said:
Where is the DL link "CAN`T WAIT TO GET SOME"
Click to expand...
Click to collapse
Initial release date is: 16/09/2014
Stone. Cold said:
Initial release date is: 16/09/2014
Click to expand...
Click to collapse
I know but couldn`t hold my entusiasm when i saw the new thread
retryer said:
I know but couldn`t hold my entusiasm when i saw the new thread
Click to expand...
Click to collapse
Just keep looking till I release, and maybe you could be the 1st to try
Thanks for your great work !! Recovery recommended?
davidmeyis said:
Thanks for your great work !! Recovery recommended?
Click to expand...
Click to collapse
CWM 5 for this device, I think...
To all my users, please do enjoy using UltraBeam REVO. It took me a while to cook this ROM and make it all perfect for all of you. So all I want is good feedback from users
Thank you, and enjoy!
WOHOO !! Downloading , and soon will share
[edit1]:
Cool boot animation
[edit2]:
Man I`m a fan of the red , BUT THIS BLUE THEME IS F**KING AWESOME !!
It booted okay from the first try , recognized the ext4 partition as internal . Will add google acc and some apps to soo how things will go, but from now I can say - you did it again THANK YOU!
is there a changelog from 1.6 version to this one?
Okay so this is so far :
I`m very hapy to see the torch actually working , everything is so smooth so you cant even guess thats it uses sd partition .
The entropy generator started okay , everything is beautifull the rom is awesome and I`m sure it took you time to make it this good.
The only problem I met was the galery app closing immediatly after its open (maybe its some problem in tke APK file so nothing stops users to download another galerry app as they typically do ).
The google acc synced OK with NO PROBLS
I decided to give you a hand here and open my eclipse to give oyu logcat so here it is :
09-17 00:08:25.459: D/dalvikvm(1526): GC_EXPLICIT freed 137K, 50% free 3254K/6407K, external 0K/0K, paused 67ms
09-17 00:08:47.801: I/ActivityManager(1036): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.alensw.PicFolder/.GalleryActivity } from pid 1149
09-17 00:08:47.891: I/ActivityManager(1036): Start proc com.alensw.PicFolder for activity com.alensw.PicFolder/.GalleryActivity: pid=1944 uid=10014 gids={1015}
09-17 00:08:48.041: D/szipinf(1944): Initializing inflate state
09-17 00:08:48.071: D/dalvikvm(1944): DexOpt: couldn't find field Landroid/content/res/Configuration;.smallestScreenWidthDp
09-17 00:08:48.071: W/dalvikvm(1944): VFY: unable to resolve instance field 9
09-17 00:08:48.081: D/dalvikvm(1944): VFY: replacing opcode 0x52 at 0x0032
09-17 00:08:48.081: I/dalvikvm(1944): Could not find method android.view.ViewConfiguration.hasPermanentMenuKey, referenced from method com.alensw.PicFolder.QuickApp.c
09-17 00:08:48.081: W/dalvikvm(1944): VFY: unable to resolve virtual method 673: Landroid/view/ViewConfiguration;.hasPermanentMenuKey ()Z
09-17 00:08:48.081: D/dalvikvm(1944): VFY: replacing opcode 0x6e at 0x0061
09-17 00:08:48.081: D/dalvikvm(1944): VFY: dead code 0x0034-0039 in Lcom/alensw/PicFolder/QuickApp;.c ()Z
09-17 00:08:48.081: D/dalvikvm(1944): VFY: dead code 0x0064-0067 in Lcom/alensw/PicFolder/QuickApp;.c ()Z
09-17 00:08:48.091: I/ActivityThread(1944): Pub com.alensw.PicFolder.FileProvider: com.alensw.PicFolder.FileProvider
09-17 00:08:48.111: W/dalvikvm(1944): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/alensw/PicFolder/JniUtils;
09-17 00:08:48.121: E/QuickApp(1944): init: java.lang.ExceptionInInitializerError
09-17 00:08:48.141: I/ActivityManager(1036): Process com.alensw.PicFolder (pid 1944) has died.
09-17 00:08:48.221: W/InputManagerService(1036): Window already focused, ignoring focus gain of: [email protected]
Something is bad in the galery.apk as i tought so this means only one thing:
YOU ROM IS BUGFREE ! YOU DID IT
---------- Post added at 12:13 AM ---------- Previous post was at 12:11 AM ----------
Will full-charge tonight and share how things go after day or two GOOD JOB! BRAVO
Its all ok ecept the screen during calls , where maybe all the text is white so it doesnt show but all other features of the rom are ok , stable , with NO A SINGLE REBOOT OR FC and very smooth overall
For non - north american users like me - just download https://play.google.com/store/apps/details?id=org.fastergps and choose where you live , so the program will fix the gps servers for your country @Stone. Cold please share this with all users of your rom (put it in the first thread ) so people woudn`t complain about gps errors
retryer said:
Its all ok ecept the screen during calls , where maybe all the text is white so it doesnt show but all other features of the rom are ok , stable , with NO A SINGLE REBOOT OR FC and very smooth overall
Click to expand...
Click to collapse
The 1st picture I didn't expect that... is that a bug, or is it the screenshot?
The 1st picture I didn't expect that... is that a bug, or is it the screenshot?
Click to expand...
Click to collapse
Same on my phone, I thought its a feature :-/
Its a bug , because there are buttond in the down part but the text is white and hidden , its a screenshot also . Fix the gallery ap - the signatyre is incorrect -says the updade , and include the ling for the gps app in your first post so the users can change their gps.conf safetly when they are from europe , because it wouldnt work otherwise.