Database Develop

CFH [Wildfire] v1.0 - Newb rom

Hi
I had the day off, and decided to have a play with the Kitchen to see what I could come up with. After following the instructions on theunlockr.com I decided to base my rom on the OpenFire v.2.3 rom. Any issues that rom had, mine will have.
I have added a few things and changed a couple of things, but in the end, this is my first rom for a device I do not have myself. I have an HTC Desire, but noticed that the Wildfire isn't getting as much love, hence that choice. I hope to get a better understanding of what it takes to make a proper custom rom at some time in the future.
Removed:
Launcher2
Added:
Launcher Pro
Titanium Backup
Rom Manager
Fancy Widget
From the OpenFire v.2.3 post:
NO HTC APPS DO NOT WORK ON THIS ROM AND I WONT TRY TO PORT THEM (but if you try and suceed please tell me and I will maybe include them!)
This ROM is from the android source there is no HTC apps or extra apps from the start it do come with spareparts and dev tools from android source. At the moment it seems a bit slow I think that is due to animations, animations can be turned of in spareparts or in the settings menu.
Features:
- Froyo aosp 2.2.1
- Root + superuser app
- Busybox
- No htc apps!
- Some google apps
- Multi language
- Darktremor Apps2SD
- Patched market
- Usb & WIFI-thetering
- JIT
- 3 in 1 reboot menu
- It may make your phone explode! (You have been warned)
Bugs / Not working:
- Video recording working (but, bad quality)
- Cant import contacts from SIM ? no read/write acess to SIM ? (can anyone confirm or deny this?)
TODO:
- Get rid of above bugs
- HTC-camera (maybe)
Thanks to:
HCDR.Jacob - for the kernel and vendor
Yopsi - for sharing package with google apps.
danne_jo - for APN stuff, and for hosting to my ROM
Sympnotic - For his patched market app
AnantK123 - For pointing out a fix for the camera app
acavella - For hosting / making a homepage dedicated just for OpenFire
Notes:
NO HTC APPS DO NOT WORK ON THIS ROM AND I WONT TRY TO PORT THEM (but if you try and suceed please tell me and I will maybe include them!)
To get app2sd to work you need an ext partition when you have that you might have todo a full wipe and reflash the ROM to get app2sd to work
When you boot up first time choose "com.android.provision"
Anything you want to know about OpenFire can be found at the OpenFire website.
CFH [Wildfire] v1.0 Fault Log
Download:
CFH [Wildfire] v1.0.zip (58 MB)
Due to posting restrictions, I am unable to post links to the Rom. I will post it as soon as possible.
In the mean time, please leave comments below.
Thanks
Chronicfathead

Reserved for future use
Reserved for future use

What did you change? We don't need roms like those. Everyone can customize his installed rom like he wants.
Why don't you stick to a phone you have and help projects that just need help instead of reinventing the wheel over and over again?
no offense, just my personal oppinion

bl1nkk said:
What did you change? We don't need roms like those. Everyone can customize his installed rom like he wants.
Why don't you stick to a phone you have and help projects that just need help instead of reinventing the wheel over and over again?
no offense, just my personal oppinion
Click to expand...
Click to collapse
None taken.
I've had my desire for a while, and decided to root it about a month ago. I have now installed a custom rom, and I'm enjoying the fiddling around. I don't have too much knowledge, apart from experiences gained in the last week or so.
I tried talking a colleague into installing a custom rom, but he said there weren't too many for the Wildfire, so I said I'd have a play. I'm treating it as a learning curve, as I've always been interested in programming, but never really had the time. I have created a (very) small program for the Mac, and have written a few batch files but thats as far as I've taken it.
In an afternoon I've set up a Linux VM, installed all the needed software and had a play to see what I can realistically do. I see this as a first step. I'm trying to talk the wife into a Wildfire so I can have one to play with!
If the consensus is I should delete the thread, then so be it.
Chronicfathead.

[ROM] GladiAtrix2 v4.2.3 (For 1.57 - CWM - Stable Release - 4/13/2011)

Update 05/10/2011: So, at this point I've just fallen too far behind the curve, and it doesn't look like I will be updating GladiAtrix any further. I'll still support v4.2.3 for 1.57 (which is pretty stable, and almost all the issues I've seen users have up to this point are the installation). I may at some point throw something together for myself to use and release it (as I don't care for the themes/mods of GingerBlur/GreyBlur), but at this point I'm doing all the mods manually and have no current plans to make a flashable zip out of it.
GladiAtrix 2 for 1.5.7 v4.2.3 CWM​News and Important Info - READ FIRST
{
"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"
}
Looks horribly out of place I know ​
04/14/2011 @ 10:00am: Download links are fixed. Sorry all! As I stated in my last post, I will be unavailable for the next few hours. I DO see your questions and I WILL answer them. Please be patient, this isn't my full-time job and I have other things that need my attention today. Thanks!
04/13/2011 @ 11:17pm - NOTICE on theme: The THEMED version does not have reboot/recovery. I've been too busy working out the other kinks to add it in. The NOTHEME version is just like v3 and older, with the reboot/recovery options intact, as well as all the other changes up to this point. That is the only difference between the two.
All the bugs with the fingerprint scanner, wifi defaulting to on, custom keyboards not working, etc. etc. should all be resolved. Please PM me or reply to the thread if you have any issues.
Version 4.2.3 is going to be considered base from here on forward. It will create a backup of all the files it changes and copy them to the root of the internal SD card. PLEASE copy this backup to some place safe. Going forward, all updates will be released on top of 4.2.3, and will create sequential backups of any new files changed, if there's a need to back them up. It does not have any feature updates since 4.2.1, just many bug fixes.
04/13/2011 @ 11:00am(ish) - NOTICE on Reboot/Recovery power menu options: These are currently removed. I added a theme, and I haven't had time to add reboot/recovery options to it yet. If someone who knows what they're doing would like to add them and send me the updated files, it would certainly expidite the process as I'm not even sure how I got them working in the first place on v1-3. Screenshots will be in the second post as soon as I get a moment to upload some.​History and SummaryCWM finally released! Sorry for taking so long with it, I'm very picky about my work and wanted to test EVERYTHING and make sure it was all working as it was supposed to. I hope the extra effort pays off and nobody has any issues with this
I've removed the script version as there's no need for it anymore. CWM is safer and does everything we need it to do with the latest version.
This is only for AT&T phones running firmware version 1.57. If you have 1.52 or 1.26 please go here first: [SCRIPT] GladRoot (Bell 0.37.4, AT&T 1.26/1.52/1.57 Supported) If you are a Bell user, DO NOT INSTALL.
If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
If you run into any issues, please PM me or post your /data/local/tmp/ga2.log here. This will help me diagnose what went wrong, in the very unlikely event something goes wrong.
Come chat with us!​Features:
Deodexed
Creates a backup of your current /system/app and /system/framework directories (This does NOT delete anything outside specific AT&T bloatware files, however)
Custom boot logo (animated version coming soon!)
AppWidgetPicker (better widget management)
Enables sideloading
Ad blocking
Installs AT&T tethering APN
Enables desktop flash content, i.e. Hulu (You MUST install flashplayer 10.2 from market prior to installing the ROM. You must also use a browser that lets you set your user agent to Desktop, such as Dolphin Browser HD)
Clears Dalvik-cache (can cause some third party apps to behave strangely, just clear their data. Known to cause issues with Launcher Pro. Reset of LP data fixes)
Removes the AT&T bloat (see second post for list of what is removed.)
Enables HDMI mirroring
Disables background media scanning (speeds phone up a LOT)
Webtop without need for dock (through micro-hdmi cable)
Xperia Arc theme (ported to Atrix by olieebur)
Preferred install location
Various speed increase enhancements to settings
Replaces stock Gallery with Miui 3D Gallery
Full market access, no more restricted apps (Currently under testing, as it doesn't seem to be working properly)
​Installation instructions:
Download and install Tenfar's latest CWM Recovery.
Download the GladiAtrix2 v4.2.3 THEME zip file here or GladiAtrix2 v4.2.3 NO THEME zip here
If you want the Hulu hack to work, install 10.2 from the market now, BEFORE installing GladiAtrix2 v4.
Put the GladiAtrix2v4.2.3 zip corresponding to the version you selected (normal or notheme) on either internal or external SD card.
Boot into recovery.
Select “Install zip from SDCARD” using the volume keys to navigate and power button to select.
Select "choose zip from sdcard" if you put it on your external SD card, or "choose zip from internal sdcard" if you put it in phone memory.
Browse to the location you put the zip.
Select GladiAtrix2v4.2.3 zip corresponding to the version you selected (normal or notheme).
Install it!
Read disclaimer below
​DISCLAIMER
This script makes significant changes to the /system files on your phone.
By downloading the files you agree that you KNOW WHAT YOU ARE DOING and that you accept responsibility if something goes wrong.
This has been tested to the best of my ability.
We are NOT responsible if this bricks your phone. Thank you.
-Management​Download LinksDownload GladiAtrix2 v4.2.3 FULL here
Download GladiAtrix2 v4.2.3 FULL NOTHEME here​Changelog:* Version 4.2.3 - Released 04/13/2011
Split the theme and notheme into their own versions
Rolled all updates up to this point into a full install
New base install version is this version, all future updates will be incremental.
Cleaned up install methods to not mess with any user settings
* Version 4.2.2 - Released 04/13/2011
Permission fix update for settings.db causing a massive number of issues
* Version 4.2.1 - Released 04/13/2011
Fixed HDMI mirror errors
Changed fingerprint to allow unrestricted market access
Added Motoblur widgets/apps back in as people seem to use them (myself included). AT&T bloat still removed.
Replaced stock MediaGallery with Miui 3D Gallery
Added ability to use webtop without dock through micro-hdmi
Minor settings changes for increased battery life/performance
Fixed issues with flash hack (recompiled the lib as it was corrupt)
Added option for preferred installed locations to Settings -> Applications
Imported Xperia Arc theme (ported to Atrix by olieebur)
* Version 3 - Released 04/10/2011
Now removes some of the Motoblur/AT&T bloat
Added custom boot logo (Animated version coming soon!)
Added HDMI mirroring support (Credit to Weichel)
Turned off stagefright media scanning
Added local.prop tweaks for performance increase
Fixed issues with tethering on non-AT&T carriers
* Version 2 - Released 04/08/2011
Initial CWM release.
Added custom flash lib for desktop flash content (i.e. hulu)
Installation logged with errors to /data/local/tmp/ga2.log
* Version 1
Initial script release.
​Notes/thanks:Special thanks to: kennethpenn for the base installation instructions, shawnbuck/dasmoover/cranch/thews/sogarth/brandon15811/(anyone else I missed, apologies if I did) for all their insight on the script, and Chainfire for the use of his .sh recovery output methods, olieebur for the great work on the theme, weichel for the HDMI mirroring trick, and everyone who helped test in IRC.​If you see any spelling errors or have any other problems, feel free to PM me or post here.
If you have any feature requests, PM ME them. Please read post #2 for my current To Do list to make sure it's not already on there. If you know how to do anything on the to do list and would like to help out, send me a PM. I will ignore any "cn u add grhpix to the statuss bar?" in the thread.​

To Do
bootanimation - Make static logo into animation
Fix reboot/recovery options - Anyone that wants to help with this is more than welcome to.
kill sound on sd mount - Possible?
Uninstall script - Coming soon!
List of Motorola/AT&T apps removed
com.telenav.app.android.cingular.apk
com.att.myWireless.apk
com.blockbuster.app.moto.apk
com.ea.nfsshift.apk
com.mobitv.client.tv.apk
com.mtag.att.codescanner.apk
com.wavemarket.waplauncher.apk
com.yellowpages.android.ypmobile.apk
com.qo.android.moto.apk
Screenshots (coming soon!)Will post screenshots of the major highlights here, but right now, I'm going to bed.​

first !! thanks

Ririal, is it possible to add the option to set "Edge network only" as the stock Android would allow?
PM'd u

When I go to run this it asked too allow superuser, but superuser never asked to allow anything on the phone? Phone just sits there?

Running silky smooth. I'll report errors if they arise.

s0dhi said:
Running silky smooth. I'll report errors if they arise.
Click to expand...
Click to collapse
When you run the .bat file did you have too allow superuser on the phone?

JayRolla said:
When you run the .bat file did you have too allow superuser on the phone?
Click to expand...
Click to collapse
Yes. There are 3 (I think?) points at which you have to allow superuser.
The user interface for the install is really well done.

JayRolla said:
When you run the .bat file did you have too allow superuser on the phone?
Click to expand...
Click to collapse
Never mind had to reboot phone a few times and then it worked.

Ririal said:
To Do
bootanimation - Anyone up to making one is welcome, I'm bad with graphics :x
preferred install location - Need to figure out how to do this.
kill sound on sd mount - Possible?
Fix typo in splash screen - Sigh.
Click to expand...
Click to collapse
there are a handful of boot animations here if anyone is interested. if there's something in particular you want, i'd be happy to give it a go. i too suck at the whole graphics thing, so i wouldn't expect too much.

Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.

This is after you have done retain root and updated and the afterupdate retain root.
Sent from my MB860 using XDA Premium App

xyrovice said:
Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.
Click to expand...
Click to collapse
You need a 1.57 rooted to proceed with this as it says in the OP. if you are at 1.26 rooted then use the retainroot in xda to get rooted on 1.57 and then use this.

Will this work on the Atrix on Bell?

itsonlym3 said:
there are a handful of boot animations here if anyone is interested. if there's something in particular you want, i'd be happy to give it a go. i too suck at the whole graphics thing, so i wouldn't expect too much.
Click to expand...
Click to collapse
I was looking for a custom one. I have a friend who's going to be whipping up some images for me, but you're welcome to take a stab at it.
xyrovice said:
Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.
Click to expand...
Click to collapse
This rom does not update you to 1.57. You will need to be on 1.57 with root before this will work.
jayhammy said:
Will this work on the Atrix on Bell?
Click to expand...
Click to collapse
No, it will not.

I have a 1.57 w/ root (using before/after update script). Will Deodexing my Atrix make it faster/snappier?

kpfury said:
I have a 1.57 w/ root (using before/after update script). Will Deodexing my Atrix make it faster/snappier?
Click to expand...
Click to collapse
A bit, yes.

Ririal said:
To Do
kill sound on sd mount - Possible?
Click to expand...
Click to collapse
If you figure this out please share how you did it.

I don't think that sound can be killed. But then again I'm no expert. Also are there any known issues with GladiAtrix?
I have it installed but can't really tell for now. Great great work man!!

Any chance of some screen shots of this theme? If we had CWM I would just flash and check it out.Thanks.
Sent from my MB860 using XDA Premium App

Ideas for a Custom Rom

Hello everyone,
I was reading all the posts about Custom Roms and I wanted to make something like an "XDA-Rom"... Maybe it would be better if I explain what I mean
Beginning from the system, I'd say it should be a very lightweight Rom (like the Gilgamesh one), so, without almost all the LG crapware. But I'd keep only few things of this softwares:
- contact manager (so far it's the best one I've found, but maybe because I lack of experience)
- keyboard (on some videos they say it's the fastest one, but I may be in error)
- LG home and Home switcher, so that we can keep the mirroring app working when needed.
Then, I'd add the last MoDaCo kernel (the ROM should be working in EXT4, if I understtod correctly, this shall make the phone faster), maybe we could make a proper boot animation, and just few app that are (in my opinion) the only really needed, like the gmail app, the calendar one and only the basic things. We could even update the baseband and root the phone directly from the rom, so that after a fresh install it's already running. I'd replace even the LG lockscreen, that is really nice, but it's too slow (when I switch on the screen, I see the home and then the locked screen, this shouldn't happen with the default lockscreen).
Ofc, any suggestion is welcome
Thanks for reading, and I hope my idea is not that bad

I agree on the bootanimation.

Only on that? d'oh, I wrote for half an hour btw, I'd add Root Explorer as default as well... but I don't know how to do, I mean, would be enough to create the ROM with the kitchen (really a nice tool!) and then edit the *img files adding the software I want in the /system/app directory? Maybe this is a noobish question, but it's the first time I even get closer to creating a custom rom

Oh, integrate BLN to have notifications would be a great idea ! (if you touch the kernel)

tiwiz said:
Only on that? d'oh, I wrote for half an hour btw, I'd add Root Explorer as default as well... but I don't know how to do, I mean, would be enough to create the ROM with the kitchen (really a nice tool!) and then edit the *img files adding the software I want in the /system/app directory? Maybe this is a noobish question, but it's the first time I even get closer to creating a custom rom
Click to expand...
Click to collapse
the root explorer is not for free.. so forget about this

Why? Install modaco and use filexplorer and delete all thing u dont want instead
Sent from my LG-P990 using XDA Premium App

For the experience, I'd like to test

Just use the online kitchen...
I was actually 30 mins from posting a pretty close ROM to what you mention here yesterday, but built the one I'd like online instead (except for some tweaks I put in laster on).
If people is more open for a ROM like this for direct download, I'm happy to compile/maintain it Just thought that it wasn't needed...

HTC Buzz Wildfire Sense 3.5 [Alpha Build Available]

Please read the whole post 1-3 before start asking anything.
Post 1 is about the rom
Post 2 is changelog
Post 3 is just good information
Salsa Sense 3.5 ROM √.
Launcher should be resized LAUNCHER.
{
"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"
}
OUTDATED!​
Alpha​
Salsa Sense ROM √​
Features :
Based on the Hintay Zero 0.12
Android Gingerbread 2.3.5
Brand new Sense 3.5
Busybox 1.18.4
Languages : English, Danish, Finnish, Norwegian, Swedish, Arabic, Bulgarian, Catalan, Czech, German, German, Greek, Spanish, French, Hebrew, Hindi, Croatian, Hungarian, Indonesian, Italian,Japanese, Korean, Lithuanian, Latvian, Dutch, Polish,Portuguese, Romanian, Russian, Slovak, Slovenian, Serbian, Thai, Tagalog, Turkish, Ukrainian, Vietnamese, Chinese.
HTC File Manager
Deodexed all files
Zipaligned all .apk for better RAM usage
Added A2SD (and dalvik cache to SD)
Edify scripted (CWM 3.X.X +)
And much more..
Don't ask for ETA I've now have a Wildfire to test my builds on (i'll borrow one very soon!) :
Will be a release as soon theres some good fixes!
Known bugs :
Bluetooth
GPS Maybe
Camera
More i don't know atm

Old Changelog from: Here
Continue Porting FromHere
Version Rebase
some UI changes thanks to Androidian
DiskDrive is now working even after reboot
New Bugs Occured:
Apps isn't correctly listed in drawer
Some GPS apps gives FC (???)
More IDK (Wifi is still a problem)
Version Alpha
Changed back to Cyanogen Kernel (due to easier base for porting)
fixed libhardware_legacy.so (wifi works partially*)
updated Play Store to 4.1.10
added Root Browser (free) by Jrummy
*(Wifi seems to be bricked if something force close, but i'm sure its a lib problem of incorrect wifi driver)
Version 0.3
Reverted back to original base (not the one I made changes in framework)
Updated kernel (built from sources on htc - based on 2.3.X)
Improved speed?
Realized audio is working, should have been working before I don't know)
Maybe some kernel changes (don't remember)
Changelog:
beta2
Updated Android Market to the latest version (outdated)
Updated Gmail to the latest version (outdated)
Updated Maps to the latest version (outdated)
Updated YouTube to the latest version (outdated)
New HTC_IME to temporary resolve the too big keyboard.
New HtcLockScreen.apk (thanks VigiDroid!)
Build.prop tweaks
Init.d tweaks
Launcher fix
Battery tweaks
Included Juwe's Ram script (thanks Juwe11!)
Changelog :
v0.1b
Huge thanks to arco68 for making it boot
Rebased on Hintay Zero 0.12 (Sense 3.5 Android 2.3.5)

Important Information
Originally Posted by SebastianFM
Originally Posted by rallapag
Hi SebastianFM,
I was wondering couple of things about your ROM port from salsa.
You have replaced few libs (from diff, it seems following were the libs that you have replaced)
Code:
libaudio.so
libaudioflinger.so
libbluedroid.so
libbluetooth.so
libbluetoothd.so
libdvm.so
libhardware_legacy.so
libhtc_acoustic.so
libjpeg.so
libm.so
libnativehelper.so
libOmxH264Dec.so
libOmxMpeg4Dec.so
libOmxVidEnc.so
libskia.so
libstagefrighthw.so
libttssynthproxy.so
libwpa_client.so
AND added
libSFM_runtime.so
I am thinking some of them you might have replaced using either CM7 or AOSP GB ROM libs, right??
or you had to re-compile them. (how did you do CM7 or AOSP - i am thinking it doesn't matter right??)
And about libSFM_runtime.so, it is not there in salsa ROM, so it must be something that you compiled,
so what exactly does this do?? why is this required, as i didn't find any such lib in Tattoo ROMs
Does this lib codes any compatibility with other hardware gps, camera, bt??
Thanks very much for all the help you have extended so far.
Hi,
I don't know how can I help you with GPS.
Changed libraries were build using AOSP Android 2.3.3_r1 source code and toolchain. I
Code:
recompiled some of them only to change prelink address,
libbluedroid.so, libbluetooth.so, libbluetoothd.so due to different BT chipset,
libaudio.so, libaudioflinger.so, libhtc_acoustic.so due to different audio chipset,
libOmxH264Dec.so, libOmxMpeg4Dec.so, libOmxVidEnc.so due to different VFE, libraries were taken from another ROM,
libdvm.so, libjpeg.so, libm.so, libnativehelper.so, libskia.so, libttssynthproxy.so, egl/libGLES_android.so due to missing floating point instructions support in MSM7200A chipset,
libnativehelper.so - this lib overrides some of JAVA native functions (due to missing floating point instructions support), new functions are loaded from libsfm_runtime.so,
libwpa_client.so - different Wi-Fi chipset, starts wlan_loader service,
libhardware_legacy.so - hex edited only, bcm4329.ko changed to wlan.ko.

when it becomes operational I would like to try ..

infernale said:
when it becomes operational I would like to try ..
Click to expand...
Click to collapse
hopefully in some days

LastStandingDroid said:
Salsa Sense 3.5 ROM √.
Launcher should be resized LAUNCHER.
Salsa Sense ROM √​
Features :
Based on the Hintay Zero 0.12
Android Gingerbread 2.3.5
Brand new Sense 3.5
Busybox 1.18.4
Languages : English, Danish, Finnish, Norwegian, Swedish, Arabic, Bulgarian, Catalan, Czech, German, German, Greek, Spanish, French, Hebrew, Hindi, Croatian, Hungarian, Indonesian, Italian,Japanese, Korean, Lithuanian, Latvian, Dutch, Polish,Portuguese, Romanian, Russian, Slovak, Slovenian, Serbian, Thai, Tagalog, Turkish, Ukrainian, Vietnamese, Chinese.
HTC File Manager
Deodexed all files
Zipaligned all .apk for better RAM usage
Added A2SD (and dalvik cache to SD)
Edify scripted (CWM 3.X.X +)
And much more..
Don't ask for ETA atm i don't have the HTC BuZZ Wildfire (i'll borrow one very soon!) :
Will be a release as soon theres some good fixes!
Known bugs :
Wi-Fi, GPS, BT doesn't work. <- Working on this!
Everything needs resizing. <- or changing DPI?
Almost every app needs fixed I guess.
Tell me please.
Download the latest version of No Limits (beta2 atm) :
Comes when theres some fix!
Guide to install the ROM :
1. Download the latest version
2. Put it in the root of your SDcard (/sdcard/)
3. Boot into CWM
4. Make a nandroid backup of your current ROM!!
5. Wipe data, cache and dalvik cache
6. Flash this .zip in CWM
7. Reboot
Credits :
Hintay, for his awesome Hintay Zero 0.12 ROM.
Arco68, for making this ROM boot , without him we couldn't do this.
VigiDroid for his help.
faizul_emizal for the launcher fix.
Juwe11 for his script.
Google
HTC
Some other people which i don't know who helped (etc MkBy)
Click to expand...
Click to collapse
We can resize all after geting the ROM component working.Instead of using sense lancher for now, you can use lancher pro or other home replacement.
Nice to view this project alive again
Sent from my HTC Wildfire using xda app-developers app

Pator57 said:
We can resize all after geting the ROM component working.Instead of using sense lancher for now, you can use lancher pro or other home replacement.
Nice to view this project alive again
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
the launcher should been fixed a long time ago?
don't quote the full topic next time. thanks
also i think i can get the wfi etc to work but i'm not sure, let me check some things first

Great to see this live again.
I'll be free for a few days by end of this month.So I'll offer some help if i could.

LastStandingDroid said:
the launcher should been fixed a long time ago?
don't quote the full topic next time. thanks
also i think i can get the wfi etc to work but i'm not sure, let me check some things first
Click to expand...
Click to collapse
Ha ok, was thinking it wasn't resised, hope you will get wifi working so.
for wifi fix try this :
http://forum.xda-developers.com/showthread.php?t=1446591

Pator57 said:
Ha ok, was thinking it wasn't resised, hope you will get wifi working so.
for wifi fix try this :
http://forum.xda-developers.com/showthread.php?t=1446591
Click to expand...
Click to collapse
can be useful!
hmm it seems like it loads wlan.ko and we don't have that file
edit i now see whats wrong
sigh i've made a proper edit at start than i looked into modules folder and saw a tun.ko i just got to be it. then i edited it to tun.ko and i thought why not to be sure to check a working wifi loading driver? and guess what i did correct the first time -__- now i will soon see what will happen
Now i'm off to flashing
Yes i got a wildfire now
EDIT: When wifi works i'll be release a build, not for daily use but i need logcat
OK great i thought i failed hex the file so it didn't boot but it booted up, now i'll soon see if it works or not

Wooow a dream comes true?! Glad u work on it and welcome back
The last time I tested this ROM the launcher was really the only thing that was almost fully resized. And that DPI changing tried a Wildfire S dev and I think he didn't managed it. You should may have a closer look at KoolSense there the WiFi is working and also the Bluetooth works halfway.
Sent from my Nexus 4 using xda premium

man
miniAndroidian said:
Wooow a dream comes true?! Glad u work on it. The last time I tested this ROM the launcher was really the only thing that was almost fully resized. And that DPI changing tried a Wildfire S dev and I think he didn't managed it. You should may have a closer look at KoolSense there the WiFi is working and also the Bluetooth works halfway.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
ok i see the problem now why wifi doesn't work, it doesn't load all needed files clearly some bad so file
setNetSharingInterfacesetUsbRndisenableEthernetSharingwifi_close_supplicant_connectioninit.svc.wpa_supplicant/data/system/wpa_supplicantwpa_supplicant/data/misc/wifi/sockets/data/misc/dhcp/data/misc/wifi/wpa_supplicant.confensure_config_file_exists/system/etc/wifi/wpa_supplicant.confrmmodwlan.driver.status/proc/moduleswlan wlancheck_driver_loadedwlan wlaninsmod/system/lib/modules/bcm4329.ko/system/lib/modules/bcm4329.ko
while it should be
init.svc.wpa_supplicant/data/system/wpa_supplicantwpa_supplicant/data/misc/wifi/wpa_supplicant.conf/system/etc/wifi/wpa_supplicant.confwlan.driver.status/proc/modulesbcm4329 bcm4329wlan.ap.driver.statustiap_drv tiap_drv/system/lib/modules/bcm4329.kofirmware_path=/system/vendor/firmware/fw_bcm4329.bin
**** there was pretty much missing information. wonder what libhardware_legacy this device is from. :victory:
ok i'm taking some time of, need to smoke
hmm it seems like i can't add somehing to the libhardware_legacy without getting in unbootable
edit i'm not sure, i may have messed up my flashable zip
ok i think i have un estimated the boot time ..
argh this boot time, this boot time i say
ok i saw that there was something bad in the zip
wonder what could be wrong, hmm

Bad news guys recently I moved to my beloved girl friend and I was stupid enough to not take my work station with me.
I'm not able to work on this unless I use a hex editor on phone but I won't be able to try it. Also I can only provide lib files instead of whole rom so if anyone have a spare phone they can use to flash and try my changes it would be really appreciated until I don't have my mac i can't fix a edited boot image to make it work with cyannogen as base.
Also I'm getting my new s4 due to my note ii is being messed up. And I'm not sure I will get it on warranty (tried some things that won't be good for the phone) but everything is back to stock so I hope they may fix it
SORRY guys I'll work on it from cell when I got time.
Best wishes last

good news guys I'll be working on this again starting today or tomorrow depending on if i feel like it. sorry for the bad updates
Sent from my official GT-I9505 powered with qualcom

i have no idea why it doesn't seem to boot, changing the wifi driver path works but adding the firmware path makes it unable to boot
i'm talking about: firmware_path=/system/etc/firmware/fw_bcm4329_apsta.bin
this is in stock rom and CM but not in the port,

LastStandingDroid said:
i have no idea why it doesn't seem to boot, changing the wifi driver path works but adding the firmware path makes it unable to boot
i'm talking about: firmware_path=/system/etc/firmware/fw_bcm4329_apsta.bin
this is in stock rom and CM but not in the port,
Click to expand...
Click to collapse
Try changing the build prop to allow the firmware changes. That might be causing the conflict. You might have to build a whole new sense kernel to deal with the wifi and bluetooth. These are just theories though i am just a noob to android development. once my exams are over I will try to contribute to this project more but that isn't till the 14th June/

Mubz_C said:
Try changing the build prop to allow the firmware changes. That might be causing the conflict. You might have to build a whole new sense kernel to deal with the wifi and bluetooth. These are just theories though i am just a noob to android development. once my exams are over I will try to contribute to this project more but that isn't till the 14th June/
Click to expand...
Click to collapse
i saw theres a missing folder which may cause it to not boot, don't know but it was missing
EDIT: yupp the missing folder made it not to boot but now the now the firmpware_path=/ is set and now its time to see what i need to do to make wifi work
libs are from CM 7 hope that my help us, also i'm running on modified CM7 boot.img so there should be less issues with wifi
hmm
I/WifiHW ( 253): wifi_load_driver enter
I/WifiHW ( 253): check_driver_loaded
I/WifiHW ( 253): insmod <- this wasn't even in our port ? neither was one file called wlan_tools (don't think thats important)

LastStandingDroid said:
i saw theres a missing folder which may cause it to not boot, don't know but it was missing
EDIT: yupp the missing folder made it not to boot but now the now the firmpware_path=/ is set and now its time to see what i need to do to make wifi work
libs are from CM 7 hope that my help us, also i'm running on modified CM7 boot.img so there should be less issues with wifi
hmm
I/WifiHW ( 253): wifi_load_driver enter
I/WifiHW ( 253): check_driver_loaded
I/WifiHW ( 253): insmod <- this wasn't even in our port ? neither was one file called wlan_tools (don't think thats important)
Click to expand...
Click to collapse
I reckon the wlan tools is some type of WiFi settings in sense 3.5. Like WiFi always on and stuff like that. Try looking at the official ROM they used to port and see if these files are in there. That might give you a clue. Glad to see you nearly cracked it.
Sent from my Nexus 4 using xda app-developers app

Mubz_C said:
I reckon the wlan tools is some type of WiFi settings in sense 3.5. Like WiFi always on and stuff like that. Try looking at the official ROM they used to port and see if these files are in there. That might give you a clue. Glad to see you nearly cracked it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i use cm7 boot.img so it loads cm7 drivers. and i saw that i missed a file or two missing wifi drivers i saw CM reffered to a map in /system/Wifi
and i didn't have that folder well its added and lets see what will be the result

Alright. I don't know what that fully means but it sounds good. Anyway you are making some big progress can't wait to try the update
Sent from my Nexus 4 using xda app-developers app

[ROM] [4.2.2] Archos 80 Cobalt - CyanogenMod 10.1

CyanogenMod 10.1 working on the Archos 80 Cobalt!
This is oma7144's ROM, I've been able to get it running under a bit of guidace from oma and I thought I'd share it here if anyone else is interested.
The original thread is here - but this ROM is designed for Odys Genio tablet, which has basically the same specs as the 80 Cobalt. (RockChip 3066 chip)
As always, only flash if you know what you are doing, I am not responsible for anything you do or break.
New Version 1.3.4
Thanks danielo83 for putting this zip together
Oma CM10.1 v1.3.4
Battery problem fixed and ROM is now ready for daily use
- CWM 6.0.1.5 recovery
- System ext4
- Internal Storage 2,5 GB
- PhabletUI & Multiuser
- Device spoofed as Nexus
- Ethernet Support
- Init.d support
- USB-Hub enabled
- Gameloft compatible
- Gamepad (PS2, XBox, ...)
- Kernel modules (cifs, tun, lan, serial)
- latest hosts, su, su-binary, busybox
- MX Video-Player, Apollo & FX Sound
- Reboot Menue, CPU Tweaker, Pimp my Rom
- Dateimanager HD (Root)
- Trebuchet & Nova Launcher
Instructions
Before you do anything, download the file below and extract everything to your desktop, find 'Oma RK30 CM10.1 Format NAND.zip' and copy to your externalSD card
then unmount and remove the externalSD, this is very important because if you try to boot after flashing the rom, you will not have access to the internal SD - which means you can't flash files from CWM or do anything basically
Boot to bootloader
Turn off the tablet
Unplug from charger and USB
Hold the 'volume down' button and then hold the 'power button' to turn the device on and boot into bootloader, keep holding both until you see the boot screen
Connect USB and you will get "Unknown Device" message in windows
Install device drivers included in the zip below under x64 or x86 depending on your system - see gavroche's root thread if you are having trouble
Open up RKandroidTool.exe as administrator (located in RKDevelopTool_v1.35 folder)
- if you have trouble try different USB ports on your computer
You should see at the bottom of the RKAndroidTool "Found RK Android Loader Rock USB"
Click 'erase IDB' button - this will only take a few seconds
Now click 'Run' button, this will take a few minutes to install the ROM
Insert your external SD card
The device will boot into CWM, now choose install zip from sdcard (not internal), install Oma RK30 CM10.1 Format NAND.zip that you copied to your external SD earlier
Reboot, and enjoy CM10.1
--------------------------------------------------------
Downloads
http://www.mediafire.com/download/15wh4o4xwhec11o/OMA_4.2.2_CM10.1_Rom.zip
--------------------------------------------------------
What is working
Wifi
Camera
Display
Touchscreen
Battery info showing
...everything apart from mentioned below
Known Problems -
Scren flicker when rotating screen,
When battery is low the tablet wont wake up from sleep and the power button will only reboot it instead of waking it up
- Thanks to danielolsman
- To "fix" this you could install "no sleep" from the play store.
--------------------------------------------------------
If anyone is interested in helping get rid of these three problems please don't be shy.
I'm not a dev and I'm looking at fixing the bugs but don't really know where to start...
Credits
oma7144, gavroche

kage00,
Thanks for your effort!!! You're breathing new life into our tablets. We (I am sure there's a very big community alongwith me) who have been waiting for this.
I don't have my cobalt with me right now but will try and install at some point and feedback how it goes.
Are you also willing to work actively on issues and improvements. I am happy to help wherever I can. Perhaps, others will join in as well.
Thanks

Looking at the forum feedback from HUKD, the rom is not far from being a stable rom for day to day use. I see following general issues raised with this rom so far
1. Waking up issues after deep sleep in case when the battery is low
2. Rotation issues
3. Default language
4. Nexus port and therefore certain apps incompatibility
As mentioned earlier, I am happy to help wherever I can.
Thanks

Hey nikunj87,
Thanks for your support! I would love to be able to work on the issues with this rom but to be honest, I'm not a dev, not even close, and I wouldn't even know where to begin to start fixing the problems.
For the moment I'm looking at putting together a kernel from Archos' source and adding overclocking, I've never built a kernel before so it's a learning curve... don't hold your breath, haha!
I just thought I'd post this rom here to see if we could get some interest in the project and maybe get a dev's (or two's) attention to take a look at the problems, but for the moment it's just you and me who are interested in this..
I think the best we can do is wait for an update to this rom from Oma (the original dev), as you mentioned all the problems with this rom on the cobalt are problems that exist with the same rom on other devices. So maybe with a new update it will work a bit better.
Unless if we can get someone else who knows what they are doing to take a look at it...

kage00 said:
Hey nikunj87,
Thanks for your support! I would love to be able to work on the issues with this rom but to be honest, I'm not a dev, not even close, and I wouldn't even know where to begin to start fixing the problems.
For the moment I'm looking at putting together a kernel from Archos' source and adding overclocking, I've never built a kernel before so it's a learning curve... don't hold your breath, haha!
I just thought I'd post this rom here to see if we could get some interest in the project and maybe get a dev's (or two's) attention to take a look at the problems, but for the moment it's just you and me who are interested in this..
I think the best we can do is wait for an update to this rom from Oma (the original dev), as you mentioned all the problems with this rom on the cobalt are problems that exist with the same rom on other devices. So maybe with a new update it will work a bit better.
Unless if we can get someone else who knows what they are doing to take a look at it...
Click to expand...
Click to collapse
willing to lend a hand tho I am only new to this stuff as well!

I tried this ROM, it seems that OMA posted an AKKU Fix here
I will trie it soon....
There are some problems with the camera; its inverted. The provides fix did not solve the problem, does someone know how to fix it ?

Akku fix does not work
Sent from my Nexus 4 using xda app-developers app

Cool! looks like we've got some attention from the devs!
So there is a new version of this ROM over at this thread
edit ----> please take note, if anyone tests this ROM you will need to keep the same kernel from the existing package in OP and use that to flash with new ROM, Otherwise you risk having a bricked device
Aparently the battery problem exists, but netlars has a possible fix on this thread if anyone can test it that would be great. My tablet is off getting fixed, I had some problems with the touchscreen.
Also Oma was asking if anyone could test this too
Are these paths there?
/sys/devices/platform/rk30-battery/startget
/sys/class/rk30_battery/rk30_battery_start_timer_work
Click to expand...
Click to collapse
If anyone can test and reply here please, then I can tell him on the other thread.
Thanks

Battery problem is solved (see original thread)
CM10.1 is now ready for daily use.
(@Kage00: maybe its possible for you to make a new zip package with the new boot image found here?)
EDIT:
made a zip package myself : CrewRKTablets_RK30_Cobalt 80 by Oma_CM10.1_v1.3.4.zip

Thanks danielo83,
Nice one, I'll update the OP,
I got news back from Archos repair about my tablet / touchscreen problem. They decided to replace the whole unit, so I'm going to sell the brand new one and get a Nexus 7, which means I won't be able to play around with this ROM anymore becuase I won't have the tablet. I'm happy to still keep the thread open and you guys can tell me if there's anything to update in the OP
Thanks
edit----------
In the new version do you still have the screen flicker artifacts on rotate?
danielo83 said:
Battery problem is solved (see original thread)
CM10.1 is now ready for daily use.
(@Kage00: maybe its possible for you to make a new zip package with the new boot image found here?)
EDIT:
made a zip package myself : CrewRKTablets_RK30_Cobalt 80 by Oma_CM10.1_v1.3.4.zip
Click to expand...
Click to collapse

Not sure if anyone will see this but I own an unrooted/untouched Archos 80 Cobalt which I haven't used for months. Decided to dig it out for my son to play with but I can hardly fit any apps on it so looking in to alternative roms.
Came across this rom which I want to flash but I'm unsure on how to start. Do I have to root and flash CWM on to the tablet before doing anything in this thread or are the instructions in this thread all that I need to do in order to flash this rom on to an unaltered tablet?

Yes you will need to be rooted first before using this ROM, please follow this thread to get root and CWM on your tablet then you can flash this ROM with the instructions in the OP
Yeah the storage space is limited for some stupid reason on the stock ROMs, that shouldn't be a problem on this ROM, also if you find you dont like this ROM there is also another custom ROM here based on stock 4.0.4 firmware with better app storage space

the new version still has the rotate "problem".
Sent from my Nexus 4 using xda app-developers app

I just wanted to say as well, that Archos have released kernel sources (downloadable from their website) that are from May or June 2013 from memory. The last stock ROM built for this device was released in February 2013. Which means if anyone wants to try their hand at compiling the kernel from Archos source, it would be a newer kernel than what you are using now and it could possibly fix any left over problems with this ROM. I don't have any spare time to do it anymore, but if anyone was interested I'm sure you could find a walkthrough on XDA to tell you how to do it easily enough.
The kernel for this ROM at the moment is still the stock kernel from the stock 4.0.4 ROM, which is working, but maybe if a newer kernel was made from the sources it may work a lot better

app space and vold.fstab
Does anyone know if this ROM exists with 6gb of app space? I currently have the supersport ROM with 6gb app space and edited the vold.fstab to swap the internal and external sd cards. I’d like to do the same with this JB ROM.
How difficult would it be to edit the ROM to change the app space?
Does this ROM use the vold.fstab to set where the internal and external sd cards are mounted? (I think this has been changed in JB 4.3 but I’m not sure about 4.2.2)
Cheers, T

To be honest I'm not sure if it is possible, but you could ask the devs who made the ROM they would probably be able to tell you if it was possible or not. Have a look over at http://www.arctablet.com
You'd need to ask oma7144 or netlars
You could try to post in this thread and see what they say

kage00 said:
Yes you will need to be rooted first before using this ROM, please follow this thread to get root and CWM on your tablet then you can flash this ROM with the instructions in the OP
Yeah the storage space is limited for some stupid reason on the stock ROMs, that shouldn't be a problem on this ROM, also if you find you dont like this ROM there is also another custom ROM here based on stock 4.0.4 firmware with better app storage space
Click to expand...
Click to collapse
Can you please tell me why I'm getting this error when trying to follow the root instructions from?
http://forum.xda-developers.com/showthread.php?t=2066972
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm using Windows 8.1 64 bit
I'm doing this with USB debugging enabled and the device switched on as this is the only way I can get the 'ARCHOS' device to show in Device Manager under 'Other Devices.
If I put the tablet in to download mode (power + vol down) I get a dead Android symbol with red exclamation, is this normal? However when I insert USB cable in to the device at this point my computer doesn't bring up the 'ARCHOS' device in Device Manager...
All I get then is this:

I don't actually have this tablet anymore, but I remember mine being a bit strange when I first tried to root it too. It can be a bit temperamental... I remember reading someone saying somewhere about leaving the charger plugged in when trying to reboot into download or recovery mode, if that doesn't work try with the USB cable (or both) plugged in while you try.
I also remember with mine I had to direct windows to the specific driver folder extracted from the zip based on which drivers you need, eg, x86 or x64 etc.
You could also look at this thread http://www.freaktab.com/showthread.php?3244-Archos-80-Cobalt-900-supersport-rom where the might be more info on root.
I'm using windows 7 though, so I don't know exactly what differences there are with win 8.
If all else fails just keep searching and reading all/any forums you can find about rooting the thing, I'm sure you'll find that someone has had the same or similar problem
good luck

kage00 said:
I don't actually have this tablet anymore, but I remember mine being a bit strange when I first tried to root it too. It can be a bit temperamental... I remember reading someone saying somewhere about leaving the charger plugged in when trying to reboot into download or recovery mode, if that doesn't work try with the USB cable (or both) plugged in while you try.
I also remember with mine I had to direct windows to the specific driver folder extracted from the zip based on which drivers you need, eg, x86 or x64 etc.
You could also look at this thread http://www.freaktab.com/showthread.php?3244-Archos-80-Cobalt-900-supersport-rom where the might be more info on root.
I'm using windows 7 though, so I don't know exactly what differences there are with win 8.
If all else fails just keep searching and reading all/any forums you can find about rooting the thing, I'm sure you'll find that someone has had the same or similar problem
good luck
Click to expand...
Click to collapse
Hi do you have any idea how to get XBMC working with this rom? XBMC just goes back to home screen whenever i try launching it?

For xbmc you will need an older version of it. The one from August seemed to be the one to use for most people with the same issues on the HP slate 7 so am guessing it will sort your issue too. A quick search on Google should locate the archives for you
Sent from my ARCHOS 80G9 using Tapatalk