Related
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
Z1 (brand unknown) is wrist watch phone with Android OS. It was first released in 4/2012 and it is Android 2.2.1. It has WiFi, AGPS, GSM/EDGE, 2 MP camera, mic, speaker, loudspeaker, capacitive touchscreen, display of 320x240, SDHC & SIM card slots etc.
As most Chinese phones it has SoC from MediaTek, MT6516 (armv5).
See my Czech review for photos: http://hodinky.blog.mobilmania.cz/2012/06/z1-hodinko-telefon-s-androidem/
Tweaks/tips for stock ROM (2.2.1)
Market/Google Play is missing in stock rom but it cam be added if you follow instructions on the page: http://www.ibuygou.com/p-z1_smart_android_2_2_watch_phone_gps_wifi_bluetooth_html-3638-usd.html (included in Clean ROM)
Default DPI is 120 however most controls are too small. Change it to 160 which will make all icons sharp. (included in Clean ROM)
Typing on tiny QWERTY soft keyboard is a pain, Flit Keyboard makes entering text much easier. (included in Clean ROM)
To enter engineering mode, dial *#*#8787#*#*
ADWLauncher EX works even better if you (see):
Disable all animations including scrolling homescreen
Disable dockbar and use swipe up instead (included in Clean ROM)
4x3 icon layout for home screen and 5x2 for drawer (included in Clean ROM)
Use something like Extended controls for toggles
Use No Lock if you don't need swipe to unlock feature.
Remove alternative Chinese markets and Chinese network account/sync providers from /system/app (included in Clean ROM)
Creating flashable dump
Use MT6516 BackUpTool for dumping your stock rom.
Use MTK_Rom_Studio_1.0.0a for converting dump into flashable format.
Flashing
Basically you need the driver: "MT6516_YuSu_USB_VCOM.inf" and flashing tool: "SP Flash Tool v1.1110". All tools can be found on the internet when searching for "MT6516 flash tools". The only necessary tools reuploaded can be found also here. (I'm not sure about the legality of these tools though.)
You have to use 32 bit Windows (I only tried XP in both VirtualBox and VMware but it could work with 32 bit Vista or 7).
Power off the watch, connect it directly to PC (no USB hub or extention cable) - new device will connect for few seconds - use it to install the driver. Unplug watch. (You may retry that few times because the watch disconnect within few seconds) Open flashing tool and select files to flash (I would recommend not to flash anything other than boot/recovery/system/data/logo), hit start and quickly connect the watch - flashing will start automatically.
Recovery
First build of ClockworkMod 5.0.2.8 seems to be working however all its features were not tested yet!
Recovery can be flashed with "SP Flash Tool" (use provided scatter file).
Rebooting to recovery from launched Android using "reboot recovery" works but I wasn't able to find working button shortcut to launch recovery directly from cold start. Please help me if you find a way!
Custom Clean ROM based on stock 2.2.1
Features
Removed alternative Chinese markets and Chinese (social) network accounts
Integration of Google apps (sync, Google Play, setup wizard etc)
DPI changed to 160 which makes the watch easier to control and the icons sharper
Preconfigured ADW Launcher, Flit keyboard
Includes root with Superuser, Busybox binaries
Minor clean-ups
So far this ROM doesn't include anything power user from XDA wouldn't be able to customize but this ROM is afford to save other users time with experiments.
Important notes:
Backing up your current ROM + data is highly recommended (use the above listed MT6516 BackUpTool)
The seller says you shouldn't do factory reset because of IMEI lost - I can't confirmed that - IMEI is kept even during factory resets so it doesn't seem to be stored in user data partition. BUT backup your current ROM anyway cause I might be wrong.
Clean ROM notes:
The first boot is slow. After the first boot, I recommend not touching the watch for 5-10 minutes because dalvik cache is rebuilding in the background and the setup wizard may lag a lot.
The default ADW launcher is configured to not have app drawer button - swipe up to open drawer
Known issue (to be fixed later): Because of DPI change - Bottom row of button in Dialer is smaller, however all buttons can be pressed
Known issue (to be fixed later): Because of DPI change - Superuser (root) confirmation dialog buttons aren't readable however the buttons are partly visible and can be pressed (press bottom left button to allow root acces)
Known issue (to be fixed later): Because of DPI change - There is small graphical glitch on the lock screen which however doesn't break anything
Flashing recovery is not needed at all. Just make sure you flash both partitions (it will erase all your data on the watch but not on SD). Follow instructions above on how to flash.
ROM download: http://www.multiupload.nl/3LHJ33CW95
or http://www.multiupload.nl/JK6NOATJ57
{
"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"
}
CM ROM
WIP, first build of CyanogenMod 7 (2.3.7) booted so I continue testing/evaluating. So far I only used stock kernel but I have source for MT6516 kernel.
Notes: WiFi chip - MediaTek MT5921 - no open source driver
Currently on hold.
Proofs
Flit Keyboard
moneytoo said:
Typing on tiny QWERTY soft keyboard is a pain, Flit Keyboard makes entering text much easier.
Click to expand...
Click to collapse
I actually have bought 3 Z1's and virtual keyboard is REALLY a pain..
Flit Keyboard makes entering text much easier ! !
Just Eight ( 8 ) >> Huge << Buttons Keyboard..
..that By Easily Sliding You Can Type:
>> All << Alphanumeric Characters And Symbols ! !
No More Accidentally Typing Wrong Characters ! !
Perfect 5..
(this Should Have Been THE Number One Android Keyboard..)
Thanks moneytoo ! !
ff
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Z1 Android Watch-Phone
From Wikipedia, the free encyclopedia:
http://en.wikipedia.org/wiki/Z1_Android_Watch-Phone
ff
Ive been thinking about buying the watch to use as a mp3 player, would you recomend it?
Sent from my NWZ-Z1000Series using xda app-developers app
Yes, I'm plugging my website, but hey, it's relevant.
I've just reviewed this device at:
http://linuxslate.com/Review_Z1_Android-2.2-Watch.html
Everything in this thread has been helpful, I just wanted to add my 2 cents.
DPI at 160 looks great. Unfortunately many apps will not fit, including keyboard, phone, and superuser prompt. Either find alternate keyboard and set superuser to auto-grant, or switch back and forth between 120 and 160 as necessary.
I like No Lock, but I find the phone wake-locking all the time until I turned No Lock off. I also like the fact that the time is there in big letters on the lock screen. It's very suitable for its watch functionality.
I did a manual backup without rooting (No need for Z4 Root)
Download and unrar MT6516 BackUpTool, but do not install anything.
On the Linux/Mac box, open the gscript folder, and open back22.sh in editor, or viewer.
Connect the watch via USB, and connect via adb shell
Cut, paste and execute each line from the back22.sh file
up to and including the last dd command in the first section - in other words
Code:
.
.
.
.
dd if=/dev/mtd/mtd11 of=/sdcard/backup_/expdb.img
Obviously, you don't do the comment lines.
exit the shell
Code:
exit
do:
Code:
adb remount
Install yaffs2image:
Code:
adb push <your_path_on_PC_to>/Install/BackUp/yaffs_back_2.2/gen/mkyaffs2image /system/bin/mkyaffs2image
Code:
adb shell chmod 4777 /system/bin/mkyaffs2image
(Again, the above is a cut and paste from the script)
Code:
adb remount
(for safety)
Code:
adb shell
Then cut and paste the remaining 3 mkyaffs2img commands.
Then:
Code:
exit
Copy the backup_ folder on the SD car to someplace safe.
If you want, you can remove mkyaffsimg:
Code:
adb remount
Code:
adb shell rm /system/bin/mkyaffs2image
Code:
adb remount
It's definitely more steps, but it leaves the system technically un-touched, un-rooted, and even returnable if you should have to.
Some more useful apps.
https://play.google.com/store/apps/details?id=com.coinsoft.android.orientcontrol
Orientation control to lock the screen in landscape mode; not free but worth it.
https://play.google.com/store/apps/details?id=itosisato.setsunasato.kokoroduyosato
Home button for soft home button in notification tray. Free.
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
Off button in notification tray. Free.
https://play.google.com/store/apps/details?id=com.opera.mini.android
Opera mini has server side compression so makes best use of the slow 3g speed, but no multitouch so zooming is difficult.
m34n1ng said:
Ive been thinking about buying the watch to use as a mp3 player, would you recomend it?
Sent from my NWZ-Z1000Series using xda app-developers app
Click to expand...
Click to collapse
It can be done, but the MotoActv might be better, because the motoactv has a headphone jack so you can use any headphones you want. On the Z1, you have to use bluetooth headphones or a bluetooth headphone adapter.
I just ordered one of these last week, should have arrived today ... glad to see this exists!
Other than configuration/display-size issues, does everything work, i.e. all hardware? I noticed you had a note about the Wifi driver not being open source, but I assume that more effects if you try the MT6516 kernel. Even if it's a closed binary, I assume you could still load it and use it though. I'm not expecting any leaps and bounds in the kernel department.
As for CWM, is any part of it executed at cold boot? If so, I imagine you'd need to implement some kind of timeout menu that could optionally enter recovery before booting the watch. This is similar to what was implemented on the Kindle Fire which also doesn't have a normal stock recovery mode.
I assume you're still evaluating CM7 so you're not ready to distribute it ... but I do hope to see more from you soon, especially a HOWTO and download links!
I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
I consider making custom rom based on stock Android but I don't know if there would be any demand. Proper integration of Google apps, Chinese apps/account providers removed, tweaked launcher/drawer settings, tweaked global dpi/dpi of apps that not fit...
To have at least something, I give you very simple app "Z1 Backlight Toggle" apk (attached in 1st post) which can turn off completely display backlight. (Needs root) I use it on my bike when I have navigation running all the time cause it indeed saves battery and backlight isn't needed at all under direct sunlight, the display is readable the same.
moneytoo said:
I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
Click to expand...
Click to collapse
That's fine, I understand how frustrating these things can be. But still, can you post information about how to backup / restore the firmware and how to flash a custom ROM? I might try playing with it myself sometime and at least having the knowledge would enable further experimentation.
WTF!!!! a wrist phone with Android OS.... This is so freaking cool!!! :thumbup:
Awesome......
Sent from my GT-S7500 using xda premium
moneytoo said:
I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
Click to expand...
Click to collapse
I have an idea ... if we can get the MTK6516 kernel to build and boot, that's one step. If we can then get Android 2.2 stock to build, and then compare it against an image of the Z1's file system, we should, in theory, be able to identify all the unique areas of the watch's Android setup. If we at least know how to build an identical watch Android from source we should be able to extend that into making Cyanogen Mod work ... or something else. I think it's worth a shot anyway!
Also for an identical kernel, there shouldn't be any need to "port" binary drivers ... ideally they're built-in or load as modules, same as any other drivers.
I consider making custom rom based on stock Android but I don't know if there would be any demand.
Click to expand...
Click to collapse
You're probably right there will be very limited demand. So I ask again, if you can at least post steps about reflashing the watch, I'll give it my best shot. I just want to be sure I can restore the watch after messing around with it. Which I'm guessing you were able to since you didn't claim any permanent damage. It seems it should be able to go into a factory restore mode which I hope will override any messed up systems.
lokeshsaini94 said:
WTF!!!! a wrist phone with Android OS.... This is so freaking cool!!! :thumbup:
Awesome......
Click to expand...
Click to collapse
It really is neat. Kind of limited, but really neat. I think if we can get any amount of control over the kernel and Android version, we can really extend the abilities of the watch. It just needs a chance...
southbird said:
I have an idea ... if we can get the MTK6516 kernel to build and boot, that's one step. If we can then get Android 2.2 stock to build, and then compare it against an image of the Z1's file system, we should, in theory, be able to identify all the unique areas of the watch's Android setup. If we at least know how to build an identical watch Android from source we should be able to extend that into making Cyanogen Mod work ... or something else. I think it's worth a shot anyway!
Also for an identical kernel, there shouldn't be any need to "port" binary drivers ... ideally they're built-in or load as modules, same as any other drivers.
Click to expand...
Click to collapse
In my opinion there's no problem with kernel, modules or libraries, we can just reuse them. The real issue I think is native android binaries such as wpa_supplicant or rild. We can either use (original) already built binaries or build new ones - but this is the problem... Original binaries depend on proprietary libraries so they "do something" important with devices. Newly build binaries just don't have that unknown functionality. Yes, reusing stock binaries might work for 2.2 but my only target so far was 2.3 since that would be real benefit for us.
southbird said:
So I ask again, if you can at least post steps about reflashing the watch, I'll give it my best shot.
Click to expand...
Click to collapse
Have a look here: http://bm-smartphone-reviews.blogspot.cz/2011/02/mtk-hd2-hd9-flashing-tutorial.html
Basically you need the driver: "MT6516_YuSu_USB_VCOM.inf" and flashing tool: "SP Flash Tool v1.1110". You have to use 32 bit Windows (I only tried XP in both VirtualBox and VMware but it could work with 32 bit Vista or 7 as well).
Power off the watch, connect it directly to PC (no USB hub or extention cable) - new device will connect for few seconds - use it to install the driver. Unplug watch. Open flashing tool and select files to flash (I would recommend not to flash anything other than boot/recovery/system/data/logo), hit start and quickly connect the watch - flashing will start automatically.
moneytoo said:
To have at least something, I give you very simple app "Z1 Backlight Toggle" apk (attached in 1st post) which can turn off completely display backlight. (Needs root) I use it on my bike when I have navigation running all the time cause it indeed saves battery and backlight isn't needed at all under direct sunlight, the display is readable the same.
Click to expand...
Click to collapse
Which navigation software are you using?
adthor said:
Which navigation software are you using?
Click to expand...
Click to collapse
No idea what he's using, but I'll say that Sygic worked when NOT navigating (doing a route caused it to force close, I'm guessing possibly out of memory??) Using OsmAnd works pretty well ... of course, it's Open Street Map with all the usual limitations.
adthor said:
Which navigation software are you using?
Click to expand...
Click to collapse
I use RMaps (https://play.google.com/store/apps/details?id=com.robert.maps&hl=en) with collection of offline maps and prepared tracks for navigation.
southbird said:
No idea what he's using,
but I'll say that Sygic worked when NOT navigating
(doing a route caused it to force close, I'm guessing possibly out of memory??)
Using OsmAnd works pretty well ... of course, it's Open Street Map
with all the usual limitations.
Click to expand...
Click to collapse
Sygic 10 works nice with Z1 using 3D maps.
Sygic 12 works nice with Z1 using 2D maps.
When attempting to navigate Sygic 12 with 3D maps enabled,
the Sygic 12 crashes and Z1 returns to Home screen.
Correction..
Sygic 12 works nice with Z1 using 3D maps
only when Autozoom is turned off:
Settings > Map > Autozoom [untick]
ff
I consider making custom rom based on stock Android but I don't know if there would be any demand. Proper integration of Google apps, Chinese apps/account providers removed, tweaked launcher/drawer settings, tweaked global dpi/dpi of apps that not fit...
Click to expand...
Click to collapse
That is exactly what needs to be done! If porting the binaries is not possible at the moment, why not go ahead with building with stock android, with proper google account and apps, and removing the chinese accounts.
Once you have tweaked launcher/drawer, tweaked dpi of apps that not fit etc done, it would be almost as good as running CM7. Any improvement would be a big improvement
I sincerely hope that you continue development, the demand for a stock ROM is sure to come as the device becomes more popular, as of now, there is nobody developing for Z1, that i know of.
apurvasrishti said:
That is exactly what needs to be done! If porting the binaries is not possible at the moment, why not go ahead with building with stock android, with proper google account and apps, and removing the chinese accounts.
Once you have tweaked launcher/drawer, tweaked dpi of apps that not fit etc done, it would be almost as good as running CM7. Any improvement would be a big improvement
I sincerely hope that you continue development, the demand for a stock ROM is sure to come as the device becomes more popular, as of now, there is nobody developing for Z1, that i know of.
Click to expand...
Click to collapse
I started cooking custom ROM based on the stock two days ago and I'm very happy with it. Proper integration of setup wizard, google apps, keyboard, dpi, orientation, better preconfigured launcher, working voice search etc.
So the thing is, most JB ROMs for TF101 (I think that's actually all ROMs but AOKP) use a userspace hack to invert the dock lid state before propagating it to the power management code in the framework. It is, of course, a solution, but it's rather ugly and it clutters the global framework with code that's actually needed for one or two devices in total.
So I suggest that instead of messing around with the userspace, we need to fix the bug in device specific code, i.e. the kernel. I've made a kernel patch long ago for AOKP, but now I'm experiencing problems with other kernels on unmodified userspace, so I decided to post it here and see if other developers/ROMs accept it.
There is already a framework for 'inverting' the result in the kernel, so I reused that, and that made a very simple patch. All it does is check for any switch input (a.k.a. the dock lid) and set its active_low flag to 1, which makes the kernel invert the received data. Since the code is in gpio-keys, it's very unlikely to conflict with any external devices.
The source for the patch is available on my GitHub, it should work with kernel, though I built it for AOKP kernel, which is stock .39 + bcmdhd.
So, framework hacks vs. kernel hacks, discuss.
K900 said:
So the thing is, most JB ROMs for TF101 (I think that's actually all ROMs but AOKP) use a userspace hack to invert the dock lid state before propagating it to the power management code in the framework. It is, of course, a solution, but it's rather ugly and it clutters the global framework with code that's actually needed for one or two devices in total.
So I suggest that instead of messing around with the userspace, we need to fix the bug in device specific code, i.e. the kernel. I've made a kernel patch long ago for AOKP, but now I'm experiencing problems with other kernels on unmodified userspace, so I decided to post it here and see if other developers/ROMs accept it.
There is already a framework for 'inverting' the result in the kernel, so I reused that, and that made a very simple patch. All it does is check for any switch input (a.k.a. the dock lid) and set its active_low flag to 1, which makes the kernel invert the received data. Since the code is in gpio-keys, it's very unlikely to conflict with any external devices.
The source for the patch is available on my GitHub, it should work with kernel, though I built it for AOKP kernel, which is stock .39 + bcmdhd.
So, framework hacks vs. kernel hacks, discuss.
Click to expand...
Click to collapse
Nice to see you again, old friend.
I have already developed like the same hack for my new CyanogenMod kernel, just that I am using a seperate c class to perform the switch each time the native asus code does receive a signal requesting to change the dock status.
So, generally, I would say this is a good idea and the way this problem should be solved.
The whole problem should stay in a low-level kernel space and never ever even require a userspace fix.
We just have to keep this on track, and maybe do a collection of how to-compile-kernels and some collection of tweaks, e.g. I can share my governor's code and so on. This should be a sticky then, so no developer for the TF101 can ever miss it.
If people request this I can do this. Just need some opinion.
So, after all, +1 to your (and mine, not yet shared) solution.
RaymanFX said:
I have already developed like the same hack for my new CyanogenMod kernel, just that I am using a seperate c class to perform the switch each time the native asus code does receive a signal requesting to change the dock status.
Click to expand...
Click to collapse
The logic's already there, just use my patch, seriously. Also, that's why you read kernel docs before coding stuff, toldya
Also I never really disappeared, you have my GTalk and I have the thread on Rootz. Don't want to post it here though, because XDA is, well, messy. And Rootz, at least for now, is less messy. Kinda. That's what I was thinking. Also keeping close to AOKP official forums.
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.
Hi,
I am back with one of my builds. Again this is just result of my hobby, feel free to use it, but do it on your own risk. Also any updates will be probably sporadic.
I wanted to publish my build as quickly as possible, becasuse I promised in another thread. So I simply took, what I have (and I am using right now). As a result there some detail I`d like to change for public release like this for the future (e.g. all the special feature enabled by default, the big dmesg buffer). Be careful. I`ll try to do better version as soon as possible. I don`t recomend this for begginers. Be sure you have backup.
This build is based on the official LineageOS code and contains several of my changes. In some cases it could be considered as fix, improvement, but sometimes a hack or even even security risk, so please read carefully following list. All the changes I did because I wanted the system on my device behave that way (at least time to time). Take it or leave it. Please note, that all the features are enabled by default. Be careful.
- built-in root support
- RIL is based on stock KitKat version (works better for me than the official version)
- the sensors libraries are also from stock KitKat (same reason as above )
- barometer sensor is correctly recognized by the system
- the menu button does, what it always did
- notification led brightness can be configured by user
- entering safe mode by holding specific keys during boot can be disabled by setprop persist.safe_mode_disabled true (this has always only annoyed me, but be sure you know you are doing)
- device wakeup by power button can be disabled when proximity and light sensors are blocked (e.g. in a pocket). Execute setprop persist.pwrbtn_proximity_block true
- external sdcard can be made world writeable by setprop persist.world_writable_sdcard true (be careful with this one, this opens a security risk)
- the notification led can blink when the battery is fully charged - enable by setprop persist.blink_when_charged true
- F2FS support
- the notification icons are also on the lock-screen as they ware in
previous Android versions. The carrier name is moved above the clock
(this cannot be turned off)
- the dmesg buffer size is increased to 16M. I set this for debugging
and remove it in next published build.
- ramdisk LZMA compression support
- sdcardfs support - This is faster replacemnt for the FUSE filesystem. I backported this for higher kernel version. Although I`ve been using this for several months without any problem, please consider this experimental. Enable with setprop persist.sys.sdcardfs
force_on
- mount directories for sdcard are protected against writing while the sdcard is not mounted (this solves a race condition problem which allows some apps to create files in there)
- there some other small changes related to my multiboot envrionment, czech translation, carrier name, etc.
Source code
In the installation zip there is a directory code_info with following content:
roomservice.xml - roomservice.xml for the build
commits - list of git repositories and commits used for the build
patches - directory tree with structure reflecting the source and containing
patches for individual projects. The idea (not always followed) is that one patch is one feature,if possible.
code1.diff - all the patches from patches directory together
code2.diff - changes which are not in patches directory
diff-commits.txt - obsolete, I`ll remove this one in the future or maybe use
it again
The only bug I know about is occasional crash of MTP, but I didn`t notice any negative consequences. There may some problem with battery charging (the display turns on time to time without no obvious reason during charging), but it may be some hardware error (bad cable or charger).
Since this is based on official LineageOS, thanks to everyone who contributed to it.
I am using this build for over a week without any problem, except those mentioned above.
Continue here, for the latest build.
UPDATE:
I totally forget about this yesterday - here are the proprietary files I used for this build proprietary-files-ocm13-skk-ril.tgz It is a mixture from the CM 13 official build and KitKat stock files, with modified ks file (then connect symbol is replaced with xonnect, so it doesn`t crash), maybe some other files and changes. I really don`t remember, I put this together during a long period of time. If you find any of your work inside, please accept my apologies and let me know. From my point of view it just works. If you want to apply the patches, then you will most probably want to change the hardcoded full path to these files in device/samsung/i9305/extract-files.sh.
UPDATE:
If you want to use anything from my patches, feel free to do so, just follow the license of the original project.
I tested it for about 4 hours for modem stability, taking the logs. All SAHARA transfers were ok, with no errors and retries. I should have mentioned your name in some post earlier
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
rodman01 said:
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
Click to expand...
Click to collapse
Thanks Use whatever you want from it just follow the license of the original project (I updated OP with similar note).
Help??? How to fix gps on this Rom plzz
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
One other thing, the MTP crash is the 'MTP host' app. I just disable this as it's only needed if you need your phone to be an MTP host for something like a digital camera, which I don't. It doesn't affect connections to your PC.
Is there an issue with the automatic execution of init.d scripts? I'm on Boeffla so it may just be that. Luckily you can tell Boeffla app to execute them anyway.
@Glenn2, thanks for testing I am not completely sure about it, but if I remember well, the compass problem is caused by the opensource sensor library (I think that just replacing the/system/lib/hw/sensors.smdk4x12.so with the one from my build should fix that). But the problem is not actually with the compass sensor, that one is ok, but in the opensource version there are missing some "fake" sensors, which provide calculated data based other "real" sensors. One of them provides orientation information, often used in apps as compass. Try some app (e.g. Androsens2) which lists all the sensors and you`ll see the difference - the "fake" ones have iNemo in their name.
I actually don`t care about the MTP crashes. It mostly happens after uninstalling some app, which doesn`t happen too often and otherwise I haven`t noticed any negative related to that. It is just annoying popup for me.
What do you mean by the question about init.d scripts?
p.a.n said:
What do you mean by the question about init.d scripts?
Click to expand...
Click to collapse
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it. I had this happen a couple of times on official LineageOS too. Not the famous mdm_hsic_pm0 which now seems to be cured at long last! I had a period of no signal when I was on the London Underground, maybe that was the cause.
Glenn2 said:
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Click to expand...
Click to collapse
There is /system/etc/init.d/* scripts, which run OK, or at least /system/etc/init.d/00banner does. There is also /system/etc/init.d/90userinit, which executes /data/local/userinit.sh. I remember that seme previous CM version there was also a user defined init.d somewhere in /data. This may what has changed, but I am not if this is your case.
Glenn2 said:
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it.
Click to expand...
Click to collapse
This on is also often on the top of my kernel wakelock list, but never that bad, always with reasonable times.
Glenn2 said:
Not the famous mdm_hsic_pm0 which now seems to be cured at long last!
Click to expand...
Click to collapse
Yes, the solution has been sitting in the Samsung kernel source for a long time ...
Glenn2 said:
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
Click to expand...
Click to collapse
Do you install the last rom ??? Or not
It is worth pointing out that after backing and restoring between roms, the SELinux attributes for efs files can become not correct. That can lead to something like this :
Code:
06-28 04:17:43.705 3799 3799 W ks : type=1400 audit(0.0:30): avc: denied { read } for name="efs1.bin" dev=mmcblk0p11 ino=8200 scontext=u:r:qcks:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
Code:
06-28 04:17:43.712 3799 3799 E kickstart: Requested ID 16, file "/tombstones/qcks/efs1.bin"
06-28 04:17:43.712 3799 3799 E kickstart: ERROR: function: open_file:80 Unable to open input file /tombstones/qcks/efs1.bin. Error 13: Permission denied
It results in not working RIL because of enforced SELinux. Running restorecon fixes the problem.
moad gastro said:
Do you install the last rom ??? Or not
Click to expand...
Click to collapse
I don't know what your question means, as there is only one ROM. I installed from the link in the OP (dated the same date as the OP).
Still using this ROM, and still very few problems.
The day before yesterday it crashed with the screen off. Had to hold power button in to restart.
And yesterday the damn wakelock. It got stuck at a time when I had no signal, and also I used the camera, so either may be relevant. It didn't seem to cause any drastic battery drain though (see images attached). I suppose when the CPU is awake but only at 200MHz and not doing much it uses little more than when it is sleeping?
Regarding init.d scripts. I added one to /system/etc/init.d that simply writes a file to /data when it runs, to test that it DID run. Script starts #!/system/bin/sh
Results:
1) rom with its own kernel - didn't run
2) rom with Boeffla kernel - didn't run
3) rom with Boeffla kernel and Boeffla Config app set to execute init.d scripts itself - did run
One more, just for fun!
Two days ago I was at the Wimbledon tennis, and the location service and/or weather widget decided I was in Boulogne-Billancourt (Paris) instead! I then opened and closed Maps, refreshed the widget and it changed to the correct location!
..
Hi,
I'm trying to install the current build using TWRP 3.0.2-1, but it gets stuck at the "Patching system image unconditionally..." step with the progressbar at around 40%. It's been sitting there for about 10 minutes. Does anyone know how that'd be fixable?`
Cheers
Latest build is ok for me. I've flashed it using TWRP 3.1.0 build from rgib
https://drive.google.com/drive/folders/0B7pwslEEF0l4Yzk2Nm1jOGRDQVU