This ROM is built from source using Android and CM repos. It is AOSP flavored, although some key CM7 elements are included. The build has gone through several iterations, and seems to be fairly complete. After the standard 30 seconds of exhaustive testing, Phone, Camera, Browser, Wifi, Market, Maps, GPS, etc. all appear functional.
This is an ODEXed build and currently uses the CM frameworks/base, along with a number of other CM components.
As of the 04JUN version, this ROM has a 2.6.35 kernel installed by default. This kernel is still in initial stages of development and testing. If you are having problems, you can trying flashing another kernel. I also recommend setting your minimum cpu frequency to 352, or you may have (even more) trouble getting the camera to work.
As of the 06JUN version, added the disable 9016 notification option to the Messaging app settings. Thanks to kushdeck/evervolv for the source for this addition. In addition, the default cpu frequency settings have been changed to 691/352.
If you are flashing over a version prior to 06JUN, please make sure to re-flash gapps as well, or you will be missing the gapps components. This has been fixed when flashing newer updates over ROMS from 06JUN forward. (i.e. 08JUN over 06JUN)
Kernel Info
While the .35 kernel used here seems to work quite well for the majority, there are some who will have issues due to the particular device being used. Please remember that this is still a work in progress and will continue to be developed, but it will take some time between versions due to the complexity involved. If your device doesn't work well with the .35 kernel, you can flash the old kernel for the time being.
KERN-2.6.29.zip
KERNEL UPDATE
The 01SEP version has a new source base combining board files from the previous version with a new source base from the GSM Hero github of Riemer and Erasmux (big thanks). After 30 seconds of exhaustive testing, and a few updates, everything appears to be working with this version. Not a lot of mileage yet, so as always, nandroid is your friend.
01-SEP-2011 Sync with AOSP/CM sources; Kernel updated to new 2.6.35.14 source; Fixed WiFi error on V1
TeamHeroC-2.3.5-01SEP-V2.zip
01-OCT-2011 Sync with CM sources; Kernel updated to 10-SEP 2.6.35.14 source; Redirected to CM Repos while kernel.org is down
This has a significant change to the source base due to the use of CM repos, and a limited amount of testing. Please be safe.
Predictive text is not currently working. It is being looked at.
TeamHeroC-2.3.5-01OCT.zip
01-OCT-2011 V2 UPDATE Sync with CM/AM sources; Kernel updated to 10-SEP 2.6.35.14 source; Redirected to CM & AM (Android Mirror) Repos while kernel.org is down
This has a significant change to the source base due to the use of different repos, and a limited amount of testing. Please be safe.
There are two versions - CM (all kernel.org repos switched to CM repos), and AM (many kernel.org repos switched to github android mirrors, others to CM).
Predictive text should now be working, along with Screenshots and USB Tether, which were also missing in the previous version.
TeamHeroC-2.3.5-01OCT-CM-V2.zip (CyanogenMod Repos)
TeamHeroC-2.3.5-01OCT-AM-V2.zip (Github Android Mirrors & CM Repos)
03-OCT-2011 Redirect and sync to CM & AM (Android Mirror) Repos while kernel.org is down. Update build repo to reflect 2.3.7 version. This is primarily a cosmetic change to get the 2.3.7 version numbering along with some other small changes.
There are two versions - CM (all kernel.org repos switched to CM repos), and AM (many kernel.org repos switched to github android mirrors, others to CM).
TeamHeroC-2.3.7-03OCT-CM.zip (CyanogenMod Repos)
TeamHeroC-2.3.7-03OCT-AM.zip (Github Android Mirrors & CM Repos)
22-OCT-2011 Sync with AOSP/CM sources; Back to single build using new Google/Android repositories. Lots of updates included from CM as well. This also includes the updated 22OCT 2.6.35.14 kernel.
TeamHeroC-2.3.7-22OCT.zip
03-NOV-2011 Sync with AOSP/CM sources; Updated to align with latest CM7. This also includes the updated 22OCT 2.6.35.14 kernel.
TeamHeroC-03NOV.zip
30-NOV-2011 Sync with AOSP/CM sources. Current version 7.2.0-RC0. Most of my effort will continue to be focused on ICS, so probably no updates other than aligning with any future major CM releases.
TeamHeroC-7.2.0-RC0-30NOV.zip
19-JAN-2012 Sync with AOSP/CM sources on 19JAN. Current version 7.2.X, since code updates, but no version updates have occurred since 7.2.0-RC0. Currently no plans for continuing updates barring unexpected CM updates.
TeamHeroC-7.2.X-19JAN.zip
22-MAR-2012 Sync with AOSP/CM sources on 22JAN. Current version 7.2.0-RC1 to align with CM update.
TeamHeroC-7.2.0-RC1-22MAR.zip
MISC
Building the ROM
This assumes that you have or are able to get a build environment set up.
repo init -u git://github.com/TeamHeroC/manifest_aosp_heroc.git
repo sync
. build/envsetup.sh
lunch aosp_heroc-eng
mka bacon
./vendor/aosp/tools/squisher
This will produce the ROM in the out/target/product/heroc/ directory.
Kernel source is the latest TeamHeroC 2.6.35 version, and can be found here.
Older Versions
21-MAY-2011 Original posted build.
AOSP-2.3.4-Heroc-21MAY
22-MAY-2011 Additional build with CMParts, FileManager, and Theme Support added.
AOSP-2.3.4-Heroc-22MAY
25-MAY-2011 Some cleanup and restore a few missing items (i.e. openvpn, rzscontrol, etc.)
AOSP-2.3.4-Heroc-25MAY
30-MAY-2011 Sync sources and update build
AOSP-HeroC-30MAY.zip
04-JUN-2011 Sync sources and update to 2.6.35 kernel [UPDATED to fix WIFI - V2]
AOSP-HeroC-04JUN-V2.zip
06-JUN-2011 Sync sources; default cpu freq 691/352; add disable 9016 notifications option [from kushdeck/evervolv]
TeamHeroC-GB-2.3.4-06JUN2011.zip
08-JUN-2011 Sync sources; fix backuptool.sh; fix autocomplete (dictionaries)
TeamHeroC-2.3.4-08JUN.zip
13-JUN-2011 Sync with AOSP/CM sources
TeamHeroC-2.3.4-13JUN.zip
01-JUL-2011 Sync with AOSP/CM sources [Updated to fix root issue]
TeamHeroC-2.3.4-01JUL-update.zip
08-JUL-2011 Sync with AOSP/CM sources, includes screenshot & gps updates.
TeamHeroC-2.3.4-08JUL.zip
24-JUL-2011 Sync with AOSP/CM sources
TeamHeroC-2.3.4-24JUL.zip
13-AUG-2011 Sync with AOSP/CM sources
TeamHeroC-2.3.4-13AUG.zip
14-AUG-2011 Sync with AOSP/CM sources; Version Change 2.3.5
TeamHeroC-2.3.5-14AUG.zip
First.
Sent from my HTC Hero using XDA App
I'm so impressed that our "ancient" Hero is getting this much development action even now
<.<
Looks for red glass
>.>
Jk...
This is awesome. Now theres like 8 or 9 gingerbread roms
Jaybob, you are a madman. When you and your friend stole that cow, and your friend...oops! Wrong movie. You are a busy little beaver JB. I can't believe all of the Hero action being developed by quality developers as well.
Just downloaded and will be trying this out after the hockey game.
Thanks!
Sweet! I'm glad to see a (nearly) pure AOSP rom. I like having the option of barebones vs full-featured CM. I hope to see this go pure AOSP... I wish the CM7 CPU controller could magically stay, though...
downloading now. =D
Everything seems to be running smoothly. No force closes or random reboots. All of the essentials work. Market did not recognize my phone so it couldn't restore my apps but that's not a big issue.
Let me know if this ROm improves battery life compared to the other AOSP or CM7.
PRGUY85 said:
Let me know if this ROm improves battery life compared to the other AOSP or CM7.
Click to expand...
Click to collapse
setCPU loaded settings min19 max691 with ondemand governor. I set my main profile to min 176 with conservative governor and added a screen off profile to set min to 19. No lag with that setup and battery life seems to be pretty good so far. Have not been able to use it for a full day but everything seems to be smooth. Will let you know the exact battery life after a full day of use off of a full charge.
On another note everything seems to be running great with this rom. Big ups to jaybob for fantastic work!
son of a mother. everytime I wanna calibrate my battery, either another update comes along or another rom. Thanks, JB.
ch1naski said:
son of a mother. everytime I wanna calibrate my battery, either another update comes along or another rom. Thanks, JB.
Click to expand...
Click to collapse
Very true! I think this will be the rom for my phone all I have ever wanted was a pure and stable gingerbread rom stripped to only the essentials and this would be it. =D
I noticed it's odex'd. Is anyone using FR with this, and if so, what mtd settings? I tried a fresh install (wiped everything) with fr at 80 18, and no dice....
So far everything is working for me too,wifi,gps, even the alarm clock works. It seems to running a lot better than aosp gb rom. I did have trouble with market not restoring apps, but I keep backups. Is there a way to disable the power control in the status notification bar. Thanks for the great work.
gapps ?
which gapps would i use ? thank u
ehusidic said:
Everything seems to be running smoothly. No force closes or random reboots. All of the essentials work. Market did not recognize my phone so it couldn't restore my apps but that's not a big issue.
Click to expand...
Click to collapse
If you are using firerat's, you should do the market fix located in the aosp/cm7 wiki which is located in the " read me" on the 1st page of the thread.
Flashing IS a gateway drug!
jrny99 said:
which gapps would i use ? thank u
Click to expand...
Click to collapse
You can use the 20110307 Universal gapps from here.
il Duce said:
<.<
Looks for red glass
>.>
Click to expand...
Click to collapse
After all the effort to go green?
Is there anyway to get the dialer screen from omg port? Ive grown fond of the slider
Related
FOR 32A, RADIO 6.35 and SPL 1.76
this port only have very little modification from original official ROM, some kernel driver tweaks, camera libs replacement, our bt firmware, sensors files and root.
first boot could be not very smooth. screen may go blank, if you would encounter this problem, just wait for a while, and press some keys. when you make all your settings done, a reboot is highly recommended. I have used it daily now.
download:
latest update [Jun 26]::
OC: http://forum.xda-developers.com/attachment.php?attachmentid=349885&d=1277499752
non-OC: http://forum.xda-developers.com/attachment.php?attachmentid=350638&d=1277631885 , under testing, plz report bugs.
changes:
HTC's battery driver
a new driver extension to support default USB netshare *
a newer sanpei helper which is reimplement **
non-OC version: screen on 528/352, screen off 240/176 ***
OC version: screen on 576/384, screen off 245/176 (4.0 in Linpack with JIT)
other fixes, many error reports in aosp kernel (which version > 2.6.29) have gone, we have a clean dmesg now
ROM itself:
apply update after you flash the ROM:
http://www.4shared.com/file/XHlI-Kdl/3pei_hero_21_alpha.html
mirror: http://www.multiupload.com/RRWFEYLPP1 , by malachaskos, thank you
wipe and flash in recovery, and you should delete the generated files (by android) in your sd card.
please make sure that you have installed driver properly. a little more details: http://forum.xda-developers.com/showpost.php?p=6180261&postcount=986
addition:
for JIT, download this: http://forum.xda-developers.com/attachment.php?attachmentid=345213&stc=1&d=1276842897
you have to set your Home Wallpaper and Lockscreen Wallpaper to something on sdcard before the first boot with JIT enabled, (and you can set them back after that: I have tried other HTC wallpapers except default). the workaround is found by klothius, thx .
if you encountered any trouble, and want it disabled, flash this: http://forum.xda-developers.com/attachment.php?attachmentid=345214&stc=1&d=1276842897
for Gallery3D, download this version: http://forum.xda-developers.com/attachment.php?attachmentid=338391&d=1275828997 , it could work with HTC Camera app in most HTC's ROM.
known issues and workaround:
keyboard light and some other led features : flash update plz
gps may need to boot with gps setting on, or you could try capychimp's gps files
official USB netsharing: flash update plz
if you find infinite logs about database queries which are generated by bt components, what I know is a reboot, or kill the bluetooth process
APN list shows nothing (unless your mobile operator is Chungwa in Taiwan), plz manually add your APN
* it could work under windows, but you must enable netshare in settings, and not in notification area. and you must disable netshare in settings if you want to use DiskDrive.
plz don't turn mobile network setting off when wifi is on. HTC's software will disable netsharing and uninstall the driver when you turn off mobile network.
** dev could set the button led timeout now.
just setprop sanpei.buttonlight.delay 20 (in sec) when phone is running, or set it in build.prop. plz report any issues.
*** I don't test the non-OC version myself yet, if you encountered any problem plz tell me, since it have lower frequency when you don't touch the phone.
and if the screen doesn't turn on during boot with OC version, plz press red button to close screen then press any other button to active the screen.
this issues happened once when first time I used this ROM after it was ported, though we don't have a kernel OCed that time. so I had said "first boot could be not very smooth" before. now I found that with higher CPU freq, it will happen more frequently.
so I won't support higher frequency at current. they are not so stable as I considered before. maybe you think that we could boot it with a lower frequency then use higher after boot. but I think if it have troubles when booting, it will have more troubles in heavily usage.
old changes:
some new commits to aosp kernel are included
qdsp driver changed to htc 2.6.29 version with some hacks
other little tweaks, not very important
for developers, many modules are included, you could check the modules folder. but I don't enable things like compcache by default. OC is not included, my phone is heated and I don't want to take a risk before I could have time to verify it carefully.
HTC Sync will work with with version 2.0.25, you can find it here (thank paultoan): http://www.htc.com/us/support/magic-rogers/downloads/ .
other pure ports:
you can find them here: http://forum.xda-developers.com/showthread.php?t=642125 .
legend port is a bit slow, but it have more features: the new way of select text、copy、wiki、translate and dictionary, etc.eris port may be faster then this one, and has been tested for a long time, but with old looks.
could someone test for us, if the new kernel binary and boot.img (in update.zip) could work with legend/eris ports? then we could use it to upgrade these ports too.
sanpei,好久不见啊，这个是基于昨天hero官方发布2.1移植的版本吗？
wuguohui109 said:
sanpei,好久不见啊，这个是基于昨天hero官方发布2.1移植的版本吗？
Click to expand...
Click to collapse
是。在这最好说英文，不然版主说不定对咱们有意见了...
yes, please write in English here, otherwise moderator may have some thoughts...
ok，Download now，thanks，haha
Can You check what languages does it have?
i think both “繁体中文&english”，thats all
sanpei how about rc e100 ? does it work?
Welcome back Sanpei!
Great thanks to sanpei
thanks
Bug ：
Footprints cam Preview no work (photo OK after shooting)
edit---
First Preview rotating, right and bottom Flicker
Second Preview rotating
looking forward to a more stable version
Nice to see you back sanpei.
Would there be any point in trying to throw your new kernel build into one of the older roms (like the legend or eris)?
@Sanpei
are you using your own kernel? cause i think bluetooth drain battery issue still exists on this rom
account1 said:
@Sanpei
are you using your own kernel? cause i think bluetooth drain battery issue still exists on this rom
Click to expand...
Click to collapse
you should turn off bt after using it. a component of bt will prevent the phone going to sleep when bt is turned on. I will try to find a solution when I have time.
I don't want to use HTC's kernel. because they have some other bugs too. fixing bugs in HTC's kernel is less valuable than our current way. and you know, maybe we should try android 2.2 later.
so we must stay at aosp kernel and adapt it to run both AOSP and HTC's ROM. and I think these jobs could be done. all the problems are just time, time and time.
btw, it's not "my own kernel", it is the aosp kernel, I just did some repairing for our purpose
and to others:
sorry, I couldn't do works which would take a lot of time at current. but I won't stop.
sanpei, there's an ongoing effort on porting the 2.6.33 kernel to the new radio, with some work already done. Maybe you could give some help to the people doing that job
sanpei said:
you should turn off bt after using it. a component of bt will prevent the phone going to sleep when bt is turned on. I will try to find a solution when I have time.
I don't want to use HTC's kernel. because they have some other bugs too. fixing bugs in HTC's kernel is less valuable than our current way. and you know, maybe we should try android 2.2 later.
so we must stay at aosp kernel and adapt it to run both AOSP and HTC's ROM. and I think these jobs could be done. all the problems are just time, time and time.
btw, it's not "my own kernel", it is the aosp kernel, I just did some repairing for our purpose
and to others:
sorry, I couldn't do works which would take a lot of time at current. but I won't stop.
Click to expand...
Click to collapse
we thank you all for your effort Sanpei
but by saying "turn off bluetooth after using it" makes me quit of trying all those custom roms with this particular kernel
bluetooth, its a feature i use all the time, every day, so i personally quit flashing until problem is solved
again, thank you for your great work here
Re: [ROM][6.35] a very pure HERO 2.1, new look and eris ...
Sanpei, can we use the cpu clock on some later phase of your rom/kernel ?
-------------------------------------
Sent via the XDA Tapatalk App
helderp said:
sanpei, there's an ongoing effort on porting the 2.6.33 kernel to the new radio, with some work already done. Maybe you could give some help to the people doing that job
Click to expand...
Click to collapse
.33 is a experimental project by Google, and our device won't get benefits from the increased digit. I will only work on kernels which will be chosen by Google and other manufacturers. and sadly, for some nonsense reason, I and some people couldn't work together.
account1 said:
we thank you all for your effort Sanpei
but by saying "turn off bluetooth after using it" makes me quit of trying all those custom roms with this particular kernel
bluetooth, its a feature i use all the time, every day, so i personally quit flashing until problem is solved
again, thank you for your great work here
Click to expand...
Click to collapse
i am really sorry for that. when I was fixing the battery drains, I don't know much about the right behaviors that bt features should have. so I just leave the prevent-sleep mechanism there because I think it is necessary.
and now I don't have enough time as before. but from you and others, I know what the right behaviors are. I will try to fix it in next release, for people who use bt heavily.
Bladyle said:
Sanpei, can we use the cpu clock on some later phase of your rom/kernel ?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
yes (we should make more things could be controlled by users in the long run), but not now.
we still have some issues that are important to other users, though personally, I don't use those features heavily.
my order:
1. lights in Sense ROM for other devices and battery drains when bt is on
2. android 2.2 or big improvements in android 2.2 (port them to daily usable ROM)
3. default USB netsharing, netsharing under windows and other features like this
4. other hardware supports and features like CPU freq control.
5. some hidden bugs in aosp sources or htc drivers we used (though they don't affect anything in most cases)
hope I could get enough time end of this month and next month, then I could repair/add one or two of them.
I only referenced the .33 kernel since that's what's used on cyanogen 5 series mod, and if it could be adapted to the new radio it would be a good way for us to have CM5 with the modifications cyanogen and otheres sometimes do to the kernel. Just my 2 cents
Hi everyone
I've managed to get a fairly good working build now of FRF91 from AOSP. I was inspired mainly by both AdamG and meLIanTQ for there excellent work on both there AOSP built ROM's, so thought I'd have a go at it myself, so here is the result
I'm building this ROM to suit my own personal needs, with various little things thrown in for good measure, but it will remain 100% AOSP source. No APK's will be modified *after* the build, all customisation on my part will be done via the overlay.
THIS IS NOT A SENSE-BASED ROM
ROM Details
Built from latest AOSP source. (FRF-91 2.2-r1.1)
2.1Mb Kernel Image Size so hopefully no problems for people with Bad Blocks
Kernel Base - 2.6.32.9 configured and compiled by myself (UV Support, no OC)
Self-modded Kernel Fix to keep phone charged at 100% while plugged in (used to drop to 89% and charge) (details >here<)
ext2, ext3 and ext4 support
cifs.ko, tun.ko and openvpn
Classic A2SD+ from my original dalvik-cache mod from Rooted 2.1 Eclair for Desire (details >here<) Copies Apps, App-Private and Dalvik-Cache to SD.
A2SD Fixed to help prevent White Screen Hangs (working with ext2 and ext3 partitions, needs testing with ext4)
Latest BusyBox (1.16.2)
Rooted with latest SuperUser 2.2 apk
Massive APN List
h264 Camcorder
Latest FRF91 Google Apps
3G/H Icon Fix to display H during HSDPA connection.
Default Launcher is LauncherPro Beta
WaveSecure installed to /system/app
setcpu.txt copied to sdcard JUST incase you want to use SetCPU to ramp down the CPU Speeds to help conserve battery life (remember, no OC or UV support in kernel, but I do intend to patch UV support in future releases)
The following items have also been removed:
Facebook (Installable from Market)
Twitter (Installable from Market)
Original Android Launcher
Amazon MP3 (Installable from Market)
Whats Working (currently from what I can tell as its what I use)
Facebook Sync (including profile pictures displaying in Phone App and Message App)
WiFi
USB & WiFi Teather
Notification LED's
Camera
NO ECHO
I've also not included items such as SpareParts, or LeoParts... SpareParts and LeoParts can be had from the Market.
Please refer to the 2nd post for a breakdown of changes/fixes/known issues with the ROM
Installation
Fresh Install
I recommend you do a FULL WIPE before you install this ROM if you are coming from another ROM.
Future Upgrades
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Just to say. Whenever I release a new Update, I always just "flash over" the existing one without a Wipe and go from there. I'm building each release with this ethos in mind, as its pretty annoying having to do a Wipe on each update!
DOWNLOAD
YOU WILL NEED THE 5.xx RADIO ROM FLASHED TO USE THIS ROM - 4.xx RADIOS ARE NOT, AND WILL NOT BE SUPPORTED SORRY!!
Get the latest RADIO's >HERE<
Also, remember this is a ROM I'm making for myself and a few friends, so I will try to sort out bugs as-and-when they are found, but as I'm still learning how to do this well, it may take a little time for me to sort!
Also during the FIRST initial boot after a fresh install, it can take about 30 seconds for LauncherPro to start responding. THIS IS NORMAL. Any further reboots by yourself, or upgrades in future (without wipes) don't have this issue.
FroYo-Desire 0.4b
Thanks & Credits
st0kes for all the info and tips in the Building Android from AOSP thread.
deovferreira/Kali- for the vendors which make all of this possible.
meLIanTQ for the invaluable help when I ran into a few issues during my initial build
AdamG & meLIanTQ for there inspiration
IntersectRaven for his HAVS Kernel Modifications
Anyone and everyone else who I've forgot to mention
Want to buy me a Toastie?? Can if you want But I'm not in it for the food
Future Additions
Add support to dynamically check and change the keys binded for unlocking the phone
Current Known Issues
Auto Brightness may not be to everyones taste.
Version History & Changelog
0.4b
Kernel UV Values tweaked to 925mV min, 1225mV max.
Conservative Power Governor now set on boot. (can be changed using SetCPU)
Updated LauncherPro to latest release
0.4a
Removed HAVS Additions from Kernel - caused problems with Trackpad & Light Sensor (CM3602).
New Kernel UV-Only based on Pershoots N1 Modifications. 950mV - 1275mV (for stability)
0.4
Recompiled Kernel with HAVS Support (925mV MIN, 1250mV MAX) - Credit >IntersectRaven<
0.3
Added SIM Toolkit
Final 100% Battery Charging Modification in place (keeps battery at 100% while plugged in)
WiFi Sleep now fixed (using own method based loosely on the official Google patch)
WiFi Sleep also fixed in respect to extremely high pings and regular dropped packets still compared to being in a Woken state (pings and packet consistency will remain constant regardless of screen being on or off)
AutoBrightness now set back to original FroYo values. Sense values used in 0.2 were draining the battery and keeping the screen far too bright in dark conditions.
0.2
Re-synced against latest AOSP Release & Kernel_MSM
Further-optimised Charging functions in Kernel
Fixed button backlight (full brightness)
Fixed Notification LED
Fixed Auto-Brightness
0.1b
Re-compiled Kernel enabling "Conservative" mode for (hopefully) better battery saving! (use SetCPU to enable this)
Added fixes to try get 3G working on Orange networks (for those who are fully unlocked with latest Radio's ONLY)
Corrected the order at which kernel modules load. Also sorted out module issue with FileSystem modules loading in the proper order.
No longer clear Vendor cache from Market (causes slowdown on initial use after flashing as upgrade)
0.1a
Initial Public Release
0.1-prerelease
First Initial Build
Fixed LED's
Added Camera Profiles
Fixed Facebook Sync
Fixed Teather
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
cgrec92 said:
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
Click to expand...
Click to collapse
Updated first post with a link to the modified source file
You sir are an absolute saint
Thanks so so much
5 STARS!
very very nice work.. good job.. i love AOSP rom.. i'll try it tomorrow.. one question. the biggest problem is wifi on OD and AOSPDesire (sleep mode). wifi is working on this rom when goes to sleep? Thanks
How would we go about manually installing the kernel fix? do we flash it?
Thanks again and sorry for my ignorance
cenkaan - What exactly is the WiFi sleep problem? I go into Settings -> Wireless & Networks -> Wi-Fi Settings.
Press Menu key, choose Advanced
Set Wi-Fi sleep policy to Never... Doesn't disconnect for me, but it does run in a low-power mode.
I've noticed using something like SpareParts, has *no* effect on this setting what-so-ever. It only works for me by doing it this way.
cgrec92 - thats the source file for the battery driver which must be compiled in with the kernel from source. As far as I know, the boot.img (my kernel) is compatible with OpenDesire (used it on there myself). It is already included in DeFrost, AOSPDesire, and I think AdamG might be adding it to his future updates as he did ask me where he could obtain the mod
i use wifi policy and set to never but this is not solution for me on other AOSP mods. Thanks for the quick reply
Well I've had the desire running all night and it kept its connection But if it is an issue, please let me know what you do for the issue to show (any other apps used to manage it) and I'll see what I can do
can't wait and i'll try it now
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I want to use this rom. i loved it
cgrec92 said:
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
Click to expand...
Click to collapse
I modified the *source* at which the kernel is compiled and built from. I then configured the base options for the kernel, compiled it, modified the various init scripts (which are supplied via the AOSP source build), and made the ramdisk, packed the boot.img... etc etc
If you wish to use this kernel on another rom (such as OpenDesire), then you will also need to copy the folder /system/lib/modules from my ROM to OpenDesire also. You will also need to manually edit /system/etc/init.d/**** script (whatever it is loading modules) or if there isn't one, create one to load ext2, ext3, ext4 and ipv6...
Bit more involving than I first made out really lol! Sorry...
cenkaan said:
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I use this rom. i loved it
Click to expand...
Click to collapse
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Ok that's enough hassle for you
Thanks so much for all your help
Fantastic developer will download your ROM as soon as i get home, thanks
thanks for the help and great rom.. and yes, what a pitty my wifi mac address is begin with 38:E7..
PaulW21781 said:
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Click to expand...
Click to collapse
The same issue does NOT occur on any HTC ROMs so am wondering what HTC has done specifically to address the problem...
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
bobo26 said:
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
Click to expand...
Click to collapse
Sense is not installed, no...
Pictures - couple are in the first post of this thread (at the bottom of it)
*update*
Updated to v0.1b, enabled new "Conservative" power governor for the CPU in the Kernel. Use SetCPU to enable this in the phone itself, will hopefully improve battery life, but will have a slight effect on performance when this option is enabled.
DO NOT POST IN THIS THREAD UNTIL YOU HAVE COMPLETELY READ THIS POST AND THE FAQ.
Since jt1134 is no longer supporting his CM9 releases here on XDA and asking people to go elsewhere for support, I have decided to start building CM9 for the Infuse.
Much of the credit goes to him for doing the initial ICS bringup for Infuse, I'm working on fixing some of the things that are not yet working. Even more goes to LinuxBozo - without his CM7 work we would be nowhere.
http://d-h.st/vN1 - 06/20/2012 build
http://d-h.st/ahW - 06/27/2012 build
http://d-h.st/Pfr - 07/28/2012 build
Installation instructions-from a Gingerbread firmware with "red CWM":
Place this release and an ICS gapps release on your SD card.
Flash this ZIP in CWM
Reboot - you will get stuck at the Samsung screen
Reboot to recovery again using the three-finger salute - hold down VolUp+VolDn+Power until the device reboots, release Power after the reboot, continue holding VolUp+VolDn
Go to Mounts and Storage and format: system, data, cache
Flash this ZIP a second time, then flash gapps
Reboot and enjoy
Coming from any AOSP-based firmware with "blue CWM":
Flash this, flash gapps, wipe. That should be all you need.
What is working:
Calls
GPS
Sound
Video playback
What is partially working:
Camera (minor flakiness, but mostly working)
Car dock audio (possibly desk dock too, untested) - Some issues with ringtone playback when docked - This is native dock audio, not using the Car Dock Redirector app workaround. Thanks go to StevenHarperUK of the GT-I9100 community for reworking CM9's dock audio code to permit this to work.
Wifi - It frequently loses connection when the device is asleep. Most likely needs some SDHCI driver tweaks to match the N7000 wifi driver.
Wifi Direct - A little glitchy but mostly working with I777/N7000. Won't talk to a P7510 (Tab 10.1) though.
Bluetooth - A2DP (music) and SCO (call audio) now works. However BT power management (LPM) is currently disabled, so BT may eat your battery when on.
Not working:
TV Output - No one has gotten MHL fully working on any Samsung device yet to my knowledge. There's some promising results from the I9100 community but it's not there yet.
Known issues:
SetCPU seems to be unable to set the minimum frequency to 100 MHz. This is one of the main reasons for holding off on OC - even stock clock code isn't working quite right
Facebook contact sync has been blocked by Google in ICS - this is universal to ICS on all devices I'm aware of. Facebook got what they deserved here.
Building - Use the Source, Luke
Kernel source is at: https://github.com/teamhacksung/android_kernel_samsung_dempsey
Device repo at: https://github.com/teamhacksung/android_device_samsung_infuse4g
To build, first prep your system for a Cyanogenmod build by following the instructions at:
http://wiki.cyanogenmod.com/wiki/Building_from_source
Once you have done the first "repo sync", at the two following lines to .repo/local_manifest.xml
Code:
<project path="device/samsung/infuse4g" name="teamhacksung/android_device_samsung_infuse4g" remote="github"/>
<project path="kernel/samsung/dempsey" name="teamhacksung/android_kernel_samsung_dempsey" remote="github" />
Run "repo sync" again
Sync https://github.com/TheMuppets/proprietary_vendor_samsung/ into vendor/samsung
Drop the contents of the attached tarball into vendor/samsung
(I really need to clean that process up...)
Run:
Code:
. build/envsetup.sh && brunch infuse4g
FAQ
Q: I get weird rainbows in recovery and when my device boots? What gives?
A: This is what happens when a Gingerbread or ICS kernel is booted on a device with Froyo bootloaders. You will need to either live with the rainbows (recovery is at least partially usable with the rainbows now) or flash Gingerbread bootloaders. Stay tuned for more info on bootloader flashing.
Unfortunately, the classic "rainbow fix" we used for Gingerbread is not compatible with how video acceleration is set up in ICS. The rainbowfix will just cause the device to crash immediately on boot. (I think this is why jt was not successful with LinuxBozo's CM7 source.)
Q: I'm getting rainbows, how do I flash Gingerbread bootloaders?
Flash the bootloaders from the file attached to this post using Heimdall as follows:
Code:
heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin
DO NOT do this unless you are experiencing rainbows, and DO NOT do this until you have confirmed you can flash less dangerous stuff (like kernels) with Heimdall. If the flash fails you will hardbrick!
Thanks to LinuxBozo for confirming, way back in the days of UCKJ2, that Heimdall can safely flash bootloaders from leaks. http://forum.xda-developers.com/showthread.php?p=18539754#post18539754 - Be warned, once you do this step there is no going back. For whatever reason the Infuse won't flash dumped bootloaders, so there is no known way to return to Froyo and Rogers Gingerbread bootloaders.
Change Log
7/28/2012:
Removed 1000 MHz cpufreq step - the extra frequency step was causing all sorts of weird derpage.
Fixed 1200 MHz step (it was using the wrong PLL settings)
Moved to open source sensor HAL
7/22/2012:
Major improvements to camera flash functionality - torch is still broken but most other flash functions work
EXIF info (including rotation) is now saved. However I had to disable JPEG thumbnail generation, which slows down viewing of images in gallery
Structural changes to the repos to make things cleaner - Once two patches get merged by CM I plan on submitting Infuse for official nightlies
CPU clock handling for GPU bus frequency was changed from a policy change (min freq bumped to 200 MHz in policy, which would cause some apps to "stick" the min at 200) to a DVFS lock. Min no longer bumps up to 200 - however any time the GPU is active it'll still lock to 200 MHz.
6/27/2012:
Discovered our device has a Broadcom BT chipset - the CG2900 is NOT used for Bluetooth. BT is now fully functional other than possible power management issues
6/20/2012:
Various upstream stuff
Wifi Direct support added - partially glitchy (see OP)
Bluetooth support brought up to CM7 levels (Audio stuff is still broken)
5/27/2012:
New wifi driver from GT-N7000 Update3 source drop: Hopefully will improve wifi for those with issues
New LPM (charging while off) code from I9100
All upstream changes since last build, including lockscreen weather
5/19/2012:
Lots of upstream CM9 changes, including theme engine and customizable lockscreen
Settings->Advanced now works. mDNIE settings (tested) and HSPA+ control (untested)
A small patch that might help wifi driver loading issues, but not guaranteed (gokhanmoral reverted it within a day in his case...)
5/2/2012:
Pulled in a few wifi fixes from gokhanmoral's I9100 SiyahKernel tree. May help those who are having wifi issues.
4/23:
Fixed wifi MAC address getting set randomly on every boot
4/22:
Misc stuff from CM9 upstream
New wifi driver backported from the I9100 update4 sources and pershoot's Tab 10.1 kernel - Fixes wifi tethering!
USB tethering removed until I can make the RNDIS driver play with the new net/wireless code - not even sure if it was working to begin with.
4/19:
No more banding in recovery (thank codeworkx for this one, exact same fix as for I9100)
FFC is no longer cropped to one corner of the sensor. Full resolution support for FFC still not implemented
Various upstream changes
Very nice any idea on how to get mtd to work? Also would that improve speed ? Thx
Sent from my SGH-I997 using xda premium
Thanks for taking this on for all of us here in the xda community.
Sent from my MB865 using xda premium
The_Zodiac said:
Very nice any idea on how to get mtd to work? Also would that improve speed ? Thx
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I believe that was primarily used to eliminate the need for Samsung's proprietary RFS/FSR modules.
It doesn't carry a speed benefit, but it's beneficial in the long run for kernel developers.
Current differences between my build and jt's last:
1) I haven't put AriesParts in yet - half of the features don't work
2) Overclock is not in yet - The overclock code from netarchy/LB is ancient and needs to be reworked. Voltage control is in there though
3) Car dock audio redirection is working, using a built-in CM9 approach instead of a separate dock audio redirector app. I had to make some changes in libaudio of aries-common to fix this. Probably some more work needs to be done here - ringtones when docked are iffy.
Great work... blindly flashing now based on developer name.
Sounds great.. I just got jt1134's build 2 installed and working..
Looking forward to seeing what you put together for us. Always great stuff coming from you!!
Entropy512 said:
Since jt1134 is no longer supporting his CM9 releases here, I have decided to start building CM9 for the Infuse.
Much of the credit goes to him for doing the initial ICS bringup for Infuse, I'm working on fixing some of the things that are not yet working.
http://d-h.st/x53 - 4/15/2012 build
Installation instructions-from a Gingerbread firmware with "red CWM":
Place this release and an ICS gapps release on your SD card.
Flash this ZIP in CWM
Reboot - you will get stuck at the Samsung screen
Reboot to recovery again using the three-finger salute - hold down VolUp+VolDn+Power until the device reboots, release Power after the reboot, continue holding VolUp+VolDn
Go to Mounts and Storage and format: system, data, cache
Flash this ZIP a second time, then flash gapps
Reboot and enjoy
What is working:
Calls
GPS
Wifi
Sound
Camera
Video playback
What is partially working:
Camera (front camera is zoomed in excessively)
Car dock audio (possibly desk dock too, untested) - Some issues with ringtone playback when docked - This is native dock audio, not using the Car Dock Redirector app workaround. Thanks go to StevenHarperUK of the GT-I9100 community for reworking CM9's dock audio code to permit this to work.
Not working:
Wifi tethering - We need far more than the HIDDEN_SSID fix CM7 required unfortunately
Bluetooth - Not working at all, not even to CM7 levels
TV Output - No one has gotten MHL fully working on any Samsung device yet to my knowledge. There's some promising results from the I9100 community but it's not there yet.
Click to expand...
Click to collapse
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Thanks for this! Did you fix/attempt to fix the problem with music coming out of the speaker when you get a notification with headphones plugged in? That's the only thing keeping me from loving ICS, since it's preventing me from listening to music at work.
kirin0ichiban said:
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Click to expand...
Click to collapse
I don't know what he's doing... All I know is he released his first build here but refuses to post any subsequent builds here, even though this is where all other Infuse development occurs. It's unreasonable to ask users to go to another forum just for ONE firmware, especially a forum with broken CSS stylesheets and a horrifically immature/irresponsible userbase. jt1134, imnuts, and Ezekeel are the only RW fans I've met that weren't complete douchebags and had technical skills to back up their bravado. Others think it's "kewl" to tell users to flash bootloaders all the time and then laugh at them if they hardbrick.
Frooty said:
Thanks for this! Did you fix/attempt to fix the problem with music coming out of the speaker when you get a notification with headphones plugged in? That's the only thing keeping me from loving ICS, since it's preventing me from listening to music at work.
Click to expand...
Click to collapse
Not yet... I'm just starting to mess with libaudio.
Awesome finally in the Dev section thanks Entropy!
Sent from my SGH-I997 using xda premium
kirin0ichiban said:
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Click to expand...
Click to collapse
1st must you quote the entire op?
Yes and no...yes jt is still building...no he is not posting on XDA...jt prefer the rootzwiki site that's where he is posting....
Check or Hold??
Entropy512 said:
I don't know what he's doing... All I know is he released his first build here but refuses to post any subsequent builds here, even though this is where all other Infuse development occurs. It's unreasonable to ask users to go to another forum just for ONE firmware, especially a forum with broken CSS stylesheets and a horrifically immature/irresponsible userbase. jt1134, imnuts, and Ezekeel are the only RW fans I've met that weren't complete douchebags and had technical skills to back up their bravado. Others think it's "kewl" to tell users to flash bootloaders all the time and then laugh at them if they hardbrick.
Not yet... I'm just starting to mess with libaudio.
Click to expand...
Click to collapse
Alright, well thanks for the quick reply. I didn't/don't know whats going on either. I'll just continue to monitor both threads and eventually things will become clearer on what he's doing. Great work on the ROM by the way! Keep it up.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
bigjoe2675 said:
1st must you quote the entire op?
Yes and no...yes jt is still building...no he is not posting on XDA...jt prefer the rootzwiki site that's where he is posting....
Check or Hold??
Click to expand...
Click to collapse
Obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
He and I clearly also have differing opinions on how to go forward. My opinion - fix what's broke until you hit something insurmountable (like fully working Bluetooth on CM7).
Then add shiny destabilizing features like overclocking...
kirin0ichiban said:
Alright, well thanks for the quick reply. I didn't/don't know whats going on either. I'll just continue to monitor both threads and eventually things will become clearer on what he's doing. Great work on the ROM by the way! Keep it up.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
Obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
Click to expand...
Click to collapse
No need to be rude to mister Joe he was only trying to help!
I'm glad its finally on XDA makes it easier to know when an update is since I only check this site
Sent from my SGH-I997 using xda premium
kirin0ichiban said:
obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
Click to expand...
Click to collapse
Actually you didn't but YW for clearing up your confusions....
Runs beautifully as advertised!
I spoke with Entropy.. I would like everyone to take note:
Your phone is lying to you when it says you are on H+ all the time. That would kill your battery. It will jump to H and 3G all the time. CM9 does not display H+, only H.
I found Alarm Free (HD) does the same thing as Touchwiz Clock (Alarm, Stopwatch, and Countdown). I rely on Touchwiz clock at work for testing devices times and at home for timing punishments and waking up in the morning... I felt this was important to mention.
NOTE: If you are looking for Linaro builds of Firefox/Fennec for Android ARMv7, those are over here.
UPDATE: Producing Beta, Aurora and Nightly builds again.
UPDATE: Mozilla has updated the build system to start creating ARMv6 builds of Beta, Aurora, and Nightly. Due to this (great!) news, I've stopped producing Debug, Default and Optimize builds of Firefox/Fennec and will only continue with Linaro builds for now.
Notes:
* These builds are ARMv6 ONLY!
* Supports Flash. v11/v10.3 recommended
* Fennec may currently only work for Android 2.2+ devices per Mozilla's Dev Team, but YMMV.
* Tested without issue on Republic Wireless LG Optimus S (LG LS670, AOSP 2.3.5, CM7).
* If you have issues with Sync, remove Nightly/Beta/Aurora installations from your PC and use Release to initiate pairing of your ARMv6 device
Troubleshooting:
* If you receive the error "Secure Connection Failed" with error code "sec_error_no_memory", you must disable TLS support:
1. browse to about:config
2. search for "tls"
3. toggle "security.enable_tls" to false
(Screenshot attached: 2012.06.15-10.24.25.jpeg)
ADBlock Plus:
* Development builds of AB+ work. (Tested with b3478). They can be found here.
-Michael
CURRENT DOWNLOADS (Mediafire)
~2013-03-15
814a3c08e5b394dd5aed5d3cb33db648 Beta 20.0 2013-03-15
557018e64da8325e88ea0fd8bfba5929 Aurora 21.0a2 2013-03-15
ffe80fd36443d9cb1d31a74d33030d7a Nightly 22.0a1 2013-03-15
OLDER DOWNLOADS
LINARO ONLY BUILDS (Mediafire)
~2012-10-31
cf3967e4d3333b032d9c056c0a3cf815 Release 16.0.2 2012-10-31 Linaro Optimize
fe97389213953d74ac8130bb8765d447 Beta 17.0 2012-10-31 Linaro Optimize
eb723bd3728ca2b53b80d83698fcf351 Aurora 18.0a2 2012-10-31 Linaro Optimize
65bcff80fa5f1278866c56de8dbfd03a Nightly 19.0a1 2012-10-31 Linaro Optimize
Build Notes to aid in testing:
* "Linaro" builds use Ray Donnelly's patched Linaro Android Toolchain version 4.6.3-2011.12
Working very nicely (except for sync), including Flash, on a rooted LG P506 (LG Thrive) running GB 2.37 with CM7-7.2 and a 2.6.35 kernel.
Let's hope sync comes to the ARM6 eventually...
Mike B. said:
Working very nicely (except for sync), including Flash, on a rooted LG P506 (LG Thrive) running GB 2.37 with CM7-7.2 and a 2.6.35 kernel.
Let's hope sync comes to the ARM6 eventually...
Click to expand...
Click to collapse
Sync is working on my ARMv6 device (Republic Wireless AOSP/CM7 LG Optimus S). I have access to another ARMv6 device to verify shortly.
That's good news since our phones are very similar, but still no luck here.
The MacBook is sending the data to the sync server, the phone is paired and connected, the sync account is active, everything looks good except that Fennec doesn't seem to know anything about the sync'd data (bookmarks, passwords, history).
Just verified on another Republic Wireless LG Optimus S that Firefox Sync is working as expected (Well... at least for that device...).
Working! After several tries, I finally managed to import/sync my data from desktop to phone.
Unfortunately, I changed too many things to be sure of what the actual problem was, but I'll attempt to narrow it down as soon as time permits.
Two things I know I changed were: install in internal memory instead of SD card, and login to the server (with security key) first instead of going directly to the pairing.Other factors, such as addons, Wifi vs. 3G, etc. are probably irrelevant.
Fennec is now back on the SD card and I'll check on whether it keeps on syncing properly.
No other issues to report (yet). Thanks for giving us this version. Firefox in sync with the MacBook will be a pleasure to use.
Update: after 12 hours, sync still behaving as it should.
Glad to hear.
I have Fennec installed on a second external partition with Link2SD and working fine.
can anyone ask or request Ted Mielczarek the guy heading firefox for armv6 to provide any info on progress please.
Dark Passenger said:
can anyone ask or request Ted Mielczarek the guy heading firefox for armv6 to provide any info on progress please.
Click to expand...
Click to collapse
What exactly are you looking for? Ted and a few other folks have fixed the ARMv6 compilation errors, but haven't yet managed to update the system for ARMv6 nightlies.
Have you tried this build?
Minor glitch: sync doesn't seem to survive a reboot.
I first noticed after my weekly CWM recovery backup, but it happens even with a plain reboot. The sync account vanished and Fennec gave me a new set of pairing codes. It was a simple matter of re-pairing from the MacBook, but in an ideal world, that account should remain just like the Google accounts.
I run Fennec on the SD card (moved with Titatnium Backup) but no data2SD. Anybody else have that problem?
It is not crashing and also connecting normally but main issue with me is that its only showing white pages after loading successfully as i can see new icons in title bar. Any idea why so? my phone is samsung galaxy3
Here my screenshots
thebenefactor said:
It is not crashing and also connecting normally but main issue with me is that its only showing white pages after loading successfully as i can see new icons in title bar. Any idea why so? my phone is samsung galaxy3
Click to expand...
Click to collapse
Can you give me more information about your phone? What is your Android OS? Chipset? Is this the right information here?:
http://www.gsmarena.com/samsung_i5800_galaxy_3-3395.php
Sorry, not familiar with your device.
Mike B. said:
Minor glitch: sync doesn't seem to survive a reboot.
Click to expand...
Click to collapse
Sync has survived reboots, reinstallations, and updates for me, but if I uninstall and reinstall the app sync has disappeared once. Not sure what the magic combo is, unfortunately.
Somehow it seems that sync is starting too early in the boot process. I'm still trying to figure out where the Fennec sync account is stored and therefore when it becomes available. I wonder if the official ARMv7 builds behave differently or if those sync issues are more generic. Either way it's not a show stopper.
Mike B. said:
Somehow it seems that sync is starting too early in the boot process. I'm still trying to figure out where the Fennec sync account is stored and therefore when it becomes available. I wonder if the official ARMv7 builds behave differently or if those sync issues are more generic. Either way it's not a show stopper.
Click to expand...
Click to collapse
It is under Settings > Accounts & Settings with your Gmail accounts, IIRC.
Yes, that's where it appears, but after a reboot it's gone and I haven't figured out yet where it might live in Titanium backups so that I could restore it.
xmixahlx said:
Can you give me more information about your phone? What is your Android OS? Chipset? Is this the right information here?:
http://www.gsmarena.com/samsung_i5800_galaxy_3-3395.php
Sorry, not familiar with your device.
Click to expand...
Click to collapse
Yes. Information is correct. Im running CM7.2 (2.3.7).
Mike B. said:
Yes, that's where it appears, but after a reboot it's gone and I haven't figured out yet where it might live in Titanium backups so that I could restore it.
Click to expand...
Click to collapse
Ah! Yeah... that would explain why it isn't working after a reboot, but I don't know why it would be missing (???).
I've updated the Nightly and changed some build settings (removing the updater, for example, since it won't work). Here it is.
thebenefactor said:
Yes. Information is correct. Im running CM7.2 (2.3.7).
Click to expand...
Click to collapse
Hrm... do you know if you need other build parameters? Or optimize breakage? Or a particular SDK/NDK version?
ahmedwwe said:
dsadsadsd
Click to expand...
Click to collapse
My feelings exactly.
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Reserved
Build 5 was pretty stable, interested to see what has changed.
Tapatalked from Desire S running Andromadus
Build 5 was first build i used of AOSP 4.2 and it was fantatic experience, i never expected 4.2 to work so flawlessly on desire s so fast after release. And to be honest i did not see many bugs.
So i flashed build 6 and i was not disapointed, as you said you will release only stable and advanced releases and it was the point with 4.2 build6.
It would be nice to see official changelog, but i have noticed some nice little resize job done and few small glitches fixed.
I just found one thing i dont know how to fix. On android keyboard swype Lithuanian dictionary doesnt work. It is not in official list until i refresh it and then it pops up and i install it ( it worked well with build 5) and with build 6 it just doesnt work, and when i return to dictionary list there is no Lithuanian dictionary again .
Sensors are not working properly. When i make a call, screen turns off even when i don't block the sensors and it stays that way till the time call is going
Sorry man posted it in wrong thread. Its for andromadus cm 10.1 but do look into the matter as its really is irritating
Sent from my Desire S using Tapatalk 2
Thanks for the info..
Why there is no Google Now on lock screen? Only unlock option...
I have latest gapps, updated Google Search etc.
Taranis said:
Why there is no Google Now on lock screen? Only unlock option...
I have latest gapps, updated Google Search etc.
Click to expand...
Click to collapse
That's just the way it is for 4.2, Google made it that way.
I thought I saw videos on YT with Google option on 4.2...
Taranis said:
I thought I saw videos on YT with Google option on 4.2...
Click to expand...
Click to collapse
Yeah, that is for devices with On Screen buttons (Galaxy Nexus or Nexus 4/7/10). For those, the buttons are replaced with a dotted circle on the lockscreen, swiping up from which opens Google Now. Since AOSP doesn't officially support any device without hardware buttons, Google probably thought that it would be best to remove the option from the lockscreen, since swiping from the buttons opens that anyways
Trouble with bluetooth
Hi,
Thanks for your work on this rom!
I would like to report an issue with the Bluetooth functionality in this (and earlier) versions of this rom. In my circumstance it doesn't produce an error of crash.
For example. My phone is connected with a handsfree carkit (parrot) and when entering the car it recognizes the phone, asks for pin code and 'gets connected'. The problem is that the phone is not visible (as usual) on the handsfree device and the overall functionality does not work.
If I can be of any assistance in this I'll gladly be of help.
Thanks for your work!
Well Google switched the bluetooth plugin in 4.2 from bluez to bluedroid. It has been causing issues across devices, even Nexus 7 has issues. As Flinny said we can't do much unless someone upstream fixes it.
Read more here...
http://forum.xda-developers.com/showthread.php?p=35093862
Tapatalked from Desire S running Andromadus
Anyone know why the sound disappear?. notifications, alarms, ringtones, ect.
Thanks for the enlightenment!
suku_patel_22 said:
Well Google switched the bluetooth plugin in 4.2 from bluez to bluedroid. It has been causing issues across devices, even Nexus 7 has issues. As Flinny said we can't do much unless someone upstream fixes it.
Read more here...
http://forum.xda-developers.com/showthread.php?p=35093862
Tapatalked from Desire S running Andromadus
Click to expand...
Click to collapse
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
- dictionaries other than English doesn't work with swype keyboard feature,
- some people wrote about bluetooth audio issues.
ROM is very smooth, hope it will be smooth in next builds. Great work!
Taranis said:
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
- dictionaries other than English doesn't work with swype keyboard feature,
- some people wrote about bluetooth audio issues.
ROM is very smooth, hope it will be smooth in next builds. Great work!
Click to expand...
Click to collapse
camera animations do lag sometimes and some pictures you take tend to not show up in gallery after you have taken them.
As for battery all i can say is :highfive: battery is almost same in all 4.0/4.1/ 4.2 roms AND it is not at all bad here. I managed to get from full charge(100%) to 81% in 30 hours. I doubt many roms can do something like this in low-med usage.
Other then that this rom is my personal favorite until someone release 4.2 rom with better theme or perfomance.
The only thing i lack in here is conservative cpu governor and maybe little undervoltage.
Taranis said:
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
Click to expand...
Click to collapse
+1
Who can tell me how can I put GPS shortcut on quick setting ??I have everything I need except GPS shortcut...
Anyone else have an issue where Calendar just wont sync at all to any Google account? I don't have the options to sync calendars under any of the google accounts I've set up on the device. Tried reflashing, clearing app data etc.
Apart from that, great rom. Super nice battery life.
noponies said:
Anyone else have an issue where Calendar just wont sync at all to any Google account? I don't have the options to sync calendars under any of the google accounts I've set up on the device. Tried reflashing, clearing app data etc.
Apart from that, great rom. Super nice battery life.
Click to expand...
Click to collapse
Clean or dirty install?
By dirty install remove Google accound(s) and then add your accound(s) again.
Worked for me!
For JB4.2 based roms (CM10.1 and AOSP4.2)
if you use a BT headset and are having problems with the mic give this a try.
download the following file.
http://andromadus.flinny.org/libbt-vendor.zip
extract it
Push it to your phone with adb - from the command line
adb remount
adb push libbt-vendor.so /system/vendor/lib
adb reboot
try it now.
Give it a try again and tell me if it all works... If all goes to plan new builds soon
Nick.