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
Hello,
I was wondering if there was an Android app like Activator on the iPhone? I have searched to the best of my abilities regarding this question but have not found a clear answer. The closest I have come to finding this answer was the app "LaunchKey." However, it does not seem to fit what I am looking for.
Reason for this search is due to my brief episode with the iPhone 3g and yes I know...(after finding out, android system is definitely better in terms of customizing and freedom) Thus during that time I came upon this app called "Activator", which is basically amazing. Now that I am back using the android system I realized the only I miss about the iPhone was that app.
So if anyone can help that would be great! Thanks!
BTW:
Background information on the iPhone jailbreak app "Activator." Basically you can launch any apps and system actions via gestures or hardware buttons. (such as long-press, short-press, double tap,etc...)
http://forum.xda-developers.com/showthread.php?t=850464
and for gestures Im not entirely sure where I saw it or or what it was called but it does exist.
Reply
Thanks for the reply, however, I did stumble upon that app but it does not really support long press, short press, double tap and other various hardware buttons. As for gestures, I guess it does not matter as much as the hardware button configuration. Basically can a button have more functions than just one ie: home button-going to home. Thanks
I'm hoping that this app exists, as its one of the first apps I discovered years ago that was auto installed after jail breaking my previous iPhone. The app basically allows you customize a very large range of settings as shortcuts.
http://m.lifehacker.com/5899492/mak...hen-you-connect-or-disconnect-your-headphones
not strongly related but here's an app which I found very useful:
https://play.google.com/store/apps/details?id=tora.mamma.swipestart
Thanks!
Thanks for your input I however have found the app "SwipePad" to be extremely useful, albeit not the original application I was looking for but it does the job Thank you again!
really!!! Android is amazing, I think is like a pocket pc, but sometimes I miss my old iPhone when I remember cydia tweeks like Activator. :silly:
mnunez2 said:
really!!! Android is amazing, I think is like a pocket pc, but sometimes I miss my old iPhone when I remember cydia tweeks like Activator. :silly:
Click to expand...
Click to collapse
LOL, yeah same here man this post is old Most of the updates in 4.2 resolved my need for Activator...though not as much options it serves well nevertheless
clikonco said:
LOL, yeah same here man this post is old Most of the updates in 4.2 resolved my need for Activator...though not as much options it serves well nevertheless
Click to expand...
Click to collapse
OMG This is what I want to say my Android Friends Iphone tweaks are more easy way to go, im wondering How can I get Activator !!! >> since 4 years im iphone user and recently bought Note 2 (still I have Iphone) this entire conversation is what im looking for Please help to get a tweaks like that even I looked Cydia substrate for Android mm no use as of know....
Widgets are great but you still have to unlock the phone and look at the screen and press it. With activator you can, for example, press the power button of the phone twice and that will initiate the flash light... this is much better when you are in need of the flash light quickly...I wish android had something like that...
Help Help .... Droid help
webvamsi555 said:
OMG This is what I want to say my Android Friends Iphone tweaks are more easy way to go, im wondering How can I get Activator !!! >> since 4 years im iphone user and recently bought Note 2 (still I have Iphone) this entire conversation is what im looking for Please help to get a tweaks like that even I looked Cydia substrate for Android mm no use as of know....
Widgets are great but you still have to unlock the phone and look at the screen and press it. With activator you can, for example, press the power button of the phone twice and that will initiate the flash light... this is much better when you are in need of the flash light quickly...I wish android had something like that...
Help Help .... Droid help
Click to expand...
Click to collapse
I believe since the time I have posted this question to the present, there have been alternatives as well as actual implementations to the hardware tweaks. Currently, there are baked in hardware tweaks in custom ROM such as CM10.1 (lock screen long press buttons do variety of different things) or software programs such as swipepad, or Trigger app (Both of which I use a lot)
My current ROM CM10.1 has the capability of accessing the flashlight from the longpress of home button while in lockscreen. Or even changing music volume and music track by volume press/longpress. This I consider the equivilent of what you were referring to.
clikonco said:
I believe since the time I have posted this question to the present, there have been alternatives as well as actual implementations to the hardware tweaks. Currently, there are baked in hardware tweaks in custom ROM such as CM10.1 (lock screen long press buttons do variety of different things) or software programs such as swipepad, or Trigger app (Both of which I use a lot)
My current ROM CM10.1 has the capability of accessing the flashlight from the longpress of home button while in lockscreen. Or even changing music volume and music track by volume press/longpress. This I consider the equivilent of what you were referring to.
Click to expand...
Click to collapse
Hi Clikonco,
Thanks for the Update, awesome response, I'm new to Android and have few questions
1) if I do Custom Rom CM10.1 can I get is back to normal Stock ROM to get warranty back ?
2) If so what would be the best procedure to install CM10.1 ?
I already root my Stock Rom with Rooting using Odin by Beginners Guide
3) So would I be able to install CM10.1 after rooting my custom Rom
4) If possible also please point me(url) to unroot custom Rom to Stock Operating system please (for future need).
5) And also I heard a lot about cm10, cm10 nightly, cm10 aopk which one is better or all these same ? I have international Note 2 with
GT- N7100 > 4.1.2 > Baseband : N7100DDDMG1 > Build no : JZ054K.N7100XXDMG1 > Kernel V: 3.0.31-1071214
confused !!!!
Please help .. Thanks a lot lot lot :good:
webvamsi555 said:
Hi Clikonco,
Thanks for the Update, awesome response, I'm new to Android and have few questions
1) if I do Custom Rom CM10.1 can I get is back to normal Stock ROM to get warranty back ?
2) If so what would be the best procedure to install CM10.1 ?
I already root my Stock Rom with Rooting using Odin by Beginners Guide
3) So would I be able to install CM10.1 after rooting my custom Rom
4) If possible also please point me(url) to unroot custom Rom to Stock Operating system please (for future need).
5) And also I heard a lot about cm10, cm10 nightly, cm10 aopk which one is better or all these same ? I have international Note 2 with
GT- N7100 > 4.1.2 > Baseband : N7100DDDMG1 > Build no : JZ054K.N7100XXDMG1 > Kernel V: 3.0.31-1071214
confused !!!!
Please help .. Thanks a lot lot lot :good:
Click to expand...
Click to collapse
**ATTENTION: any of the information I have provided are based on my own experience/knowledge/research. IT IS IMPERATIVE(important) that you do your own research to double check my information and advice. If ever in DOUBT, ask/research around. (or dont follow through is usually the safest option) YOU are ultimately responsible for what you do with YOUR device, if you don't believe this, please do not continue dabbling in this area.
You should be able to do that, to "unroot" your phone, but it depends on the device as well as the instructions that other developers/rooters have given. (meaning not 100% probable, you need to do more research)
*JUST NOTICED YOU SAID YOU ARE ROOTED
-To get Stock ROM, just download the appropriate ROM zip files and then flash it.
-if you want to get warranty back, you will have to follow instructions for your device on how to unroot. (if even possible)
Follow the instructions given on the cyanogenmod website, usually involves flashing and wiping. (sounds like you have a samsung phone )
Based on question 3 statement, I believe you have to do MORE research. (as this is an extremely basic idea of rooting, unless of course I misread or the question was mistyped) Here is where you can start:CM about
Again, you have to do MORE research yourself, google is your friend for that. There is no one size fits all unrooting method.
Cyanogenmod (also known as CM) has an software release life cycle. (not counting the M snapshot nor experiments) You have Stable>Nightly> Release Candidates(RC).
Taken from this Forum
bassmadrigal:
Stable is after all the features desired by the CM devs have been put in and the code has been tested. Snapshots (M builds) are builds done roughly once a month that has had some testing to make sure things are mostly working and released to the public. These are the first builds that allow official bug reports on the project manager site, https://jira.cyanogenmod.org. Nightlies are automated builds that are built, well, every night. There is no human interaction with these and they are largely there just to see if the code added throughout the day will compile. As far as the devs are concerned, there are no bad builds with the nightlies, because if it doesn't build, that is news to let them know that something is screwed up in the code. They don't accept any bug reports on these builds.
Generally, the nightly builds, while extremely experimental and considered bleeding-edge, tend to be relatively stable and mostly bug-free. Many people use the nightlies as their so-called daily-driver, meaning that any bugs that they may have aren't so severe that they want to switch to a different version. For my Nexus 4, as soon as I got it I switched to a nightly build and haven't had any bugs pop up.
Also, all builds are full builds, so if you switch to a nightly, you aren't required to flash every single nightly. You can do it as you see fit. I've been known sometimes to flash a build every day, but then I've gone a month in between updating. Just grab the latest version you want to flash and flash that one.
Click to expand...
Click to collapse
Similar answer regarding AOPK (Android Open Kang Project:What Is AOKP ROM? How Is It Different From CM9? All You Ever Wanted To Know About
Hope these answered/helped you. I intentionally did not include some information such as unrooting because you will have find them yourself Alright, already spent too much time on this post, im out for now.
BTW: if you or anyone finds incorrect information in this post, please feel free to correct me. Thank you!
clikonco said:
Hello,
I was wondering if there was an Android app like Activator on the iPhone? I have searched to the best of my abilities regarding this question but have not found a clear answer. The closest I have come to finding this answer was the app "LaunchKey." However, it does not seem to fit what I am looking for.
Reason for this search is due to my brief episode with the iPhone 3g and yes I know...(after finding out, android system is definitely better in terms of customizing and freedom) Thus during that time I came upon this app called "Activator", which is basically amazing. Now that I am back using the android system I realized the only I miss about the iPhone was that app.
So if anyone can help that would be great! Thanks!
BTW:
Background information on the iPhone jailbreak app "Activator." Basically you can launch any apps and system actions via gestures or hardware buttons. (such as long-press, short-press, double tap,etc...)
Click to expand...
Click to collapse
Use xposed addition in xposed
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.
Bit confusing here, as I understand that ROMs and kernels for the Optimus V (VM670) are incompatible with the P500. I don't see much for the VM670 in the Android Development section.
I recently flashed BobzHome. The camera apps occasionally freeze, which I blame on the camera drivers in the kernel, and when overclocking the only governor that doesn't freeze the phone is Performance - again, points towards the kernel.
ICS for the VM670 seems to be a downgrade from Gingerbread because there is no HW acceleration. "Inferior Human Organs" is not a comforting name for a ROM.
Is there a list of ROMs and kernels for the VM670?
There's tons of roms out there. I can't post links, because I'm new to xda, but you should be able to google these and figure out where the ov roms are.
I love theKraven's cold as ice (cai) ics rom. It's build for the S, but works great on the V with the virgin patch. Basically everything works except native tethering. It's as fast and smooth as I've ever seen my phone.
BobZhome's jb and ics are both good, but Bob hasn't had a lot of time to fix bugs, but it looks like he may be getting back into it.
Tdm's Quatrimus ics is also good, but same as BobZ, hasn't been updated in a while.
Thatguylurkin ported icysnap using cai as a base that is cool, but could use an update. I'm hopeful about that.
Then there's the gb roms, For the most part they are solid. Most overclock well and are fully functional. This list is not comlpete, but these are ones I've tried and like (in no particular order):
Mrg666's mirage build
Leslie Ann's harmonia build
Earthnfire78's om-mandylion
Tgl's gingersnap port
Sellers86's cyanmobile experience port
Beyond that, a few good ports from clodfelterac and ilikechicken, and there's tons of other quality froyo and gb roms. Sorry if i missed anyone, those are just the ones that come to mind.
Recoveries:
cwm is the gold standard, imho. There's a few options, BobZhome, green, Earthnfire78's zen garden
New Cot 2.1 is great.
Twrp from theKraven is fun and cool.
People like Xionia, but i never found the right .img.
Sent from my GT-P7310 using xda app-developers app
Thanks. But none of the JB or ICS ROMs support hardware acceleration, right?
And from my own research, not all of the VM670 ROMs that you say are solid, are solid.
And which of those ROMs support overclocking?
EEngineer said:
Thanks. But none of the JB or ICS ROMs support hardware acceleration, right?
And from my own research, not all of the VM670 ROMs that you say are solid, are solid.
And which of those ROMs support overclocking?
Click to expand...
Click to collapse
for ics omx libaries has been released
so their should be hw accelaration in ics
roms
I guess solid is a relative term. I would call most of those solid in that all of the key functions work, and they don't tend to crash. Hardware acceleration is still an issue, and idk if it will ever be fully addressed on the ov, but at least Kraven has fixed hq video/youtube in cai. That was one of the main issues that people said would never be fixed without hardware acceleration.
There is an egl patch to force gpu rendering, but idk if it really makes a noticeable difference.
As far as oveclocking, in my experience, none of the ics/jb roms run well over 600. They also can't handle underclocking well, so you need to raise your min clock speed to 480
In general the gb roms overclock well into the 700-800 range, but it depends on the specific rom and your specific phone.
So if I want to overclock, I'm going with a gingerbread ROM.
BobZHome is crashing on me, especially when I try to use the camera, so I blame the kernel because camera drivers are in the kernel.
Can you recommend a good kernel that overclocks well?
If that doesn't work, can you recommend a STABLE GB ROM that overclocks well?
EEngineer said:
So if I want to overclock, I'm going with a gingerbread ROM.
BobZHome is crashing on me, especially when I try to use the camera, so I blame the kernel because camera drivers are in the kernel.
Can you recommend a good kernel that overclocks well?
If that doesn't work, can you recommend a STABLE GB ROM that overclocks well?
Click to expand...
Click to collapse
Mirage was used as the base for a lot of the ports, and has a good reputation for overclocking. Harmonia 2 is also well developed.
In general, I don't think there is much of a speed difference between the overclocked gb roms and the non-overclocked cai.
I would start by trying cai and mirage, and move on from there. I think those two will definitely suit your needs, and you'll have to decide which you like better.
ps. I just realized we are conversing on two threads. Sorry, sometimes I don't look at whom I'm talking to.
You know, I just realized we are conversing on two threads, too!
Let's keep it on this thread? The title is more appropriate.
I'm going to stick with GB.
Does USB mass storage work for Mirage?
It does.
WOW! Installed Mirage and boy am I happy! Runs like a champ, overclocked up to 787MHz and so far no problems!
One issue, instead of a Google account, Add Account asks "Add an Exchange account." How do I add my Google account?
Also seems that LGCamera doesn't like the VM670.
EEngineer said:
WOW! Installed Mirage and boy am I happy! Runs like a champ, overclocked up to 787MHz and so far no problems!
One issue, instead of a Google account, Add Account asks "Add an Exchange account." How do I add my Google account?
Also seems that LGCamera doesn't like the VM670.
Click to expand...
Click to collapse
Stupid question, but did you install gapps, and did you get the normal setup process, starting with tapping the big green android?
Can you go to settings, accounts and sync and add your Google account?
Sent from my LG-VM670 using xda app-developers app
upconvert said:
Stupid question, but did you install gapps, and did you get the normal setup process, starting with tapping the big green android?
Can you go to settings, accounts and sync and add your Google account?
Click to expand...
Click to collapse
When I go to Settings > accounts and sync, when I add an account it only asks for an Exchange account.
I had installed Mirage over my existing install, so I kept all my apps. I'll reinstall gapps and see what happens.
@upconvert, with Mirage can you tell me what are your CPU settings for Min/Max & governor?
What rom were you coming from? I'm pretty sure that there's a "first time setup" included in the gapps that will tak care of that. I think it also includes the google sync that will let you add it from that menu.
upconvert said:
What rom were you coming from? I'm pretty sure that there's a "first time setup" included in the gapps that will tak care of that. I think it also includes the google sync that will let you add it from that menu.
Click to expand...
Click to collapse
I was using BobzHome. But that's not my problem. This phone keeps crashing on me!
What are the recommended settings for Performance? Maybe I'm running out of memory?
The first thing I would recommend is a full wipe before flashing. You can back up your apps with tibu or mybackup root first. I know it's a pain, but it's hard to figure out what's causing crashes when you're working off a dirty flash.
As far as performance settings I would say to start your min clock speed at 480, and then experiment with the max clock speed. Start high and take it down a notch every time it crashes until it stops crashing, then go one notch lower to be safe. Once you have your max setting, then you can do the opposite with the min speed. Start it low and click it up after any crashes.
I also like 16 bit transparency, allow ksm and purging, and disable dithering.
Well, I did what you said and did a full wipe. From the recovery menu I wiped cache and data, cleared and formatted Davlik, formatted all the partitions.
Installed Mirage and everything ran fine! I installed gapps and that fixed the Google login. Installed DroidWall, then AntTek App Manager, everything O.K. Installed Titanium Backup, ES File Explorer, inSSider, MX Player, QuickPic, TuneIn Radio.
Played with all these for awhile and everything seems O.K. then installed Radar Now to really start pushing the limits. Everything O.K.
I then installed Google Maps and that's when it hit the fan. Crashed @600MHz while running Maps. Crashed on next boot and every boot after that. Crashed within about a minute of each boot. It then became a race to boot the phone and get to AntTak App Manager fast enough to freeze Maps. After a frustrating 20 minutes I finally got there fast enough and froze Maps. My OV froze in one last protest, I pulled the battery and started it up and everything's fine now.
Maps likes to run in the background so I guess it's doing something nasty. I'm CPU max at 729MHz and it's flawless. Gotta find a good offline GPS map program.
EEngineer said:
Thanks. But none of the JB or ICS ROMs support hardware acceleration, right?
And from my own research, not all of the VM670 ROMs that you say are solid, are solid.
And which of those ROMs support overclocking?
Click to expand...
Click to collapse
..
It seems that contributing to LOS building ROM is not anymore tolerated, this post is deleted.
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Thanks for setting up a distinct thread. Things were getting confusing!
john_matrix said:
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Click to expand...
Click to collapse
Hey John great idea with opening a new Thread because i also think its really confusing already
john_matrix said:
@Scavenger87: Steel01 advised to let 15.1 (I think he is right because it's too old and because lot of changes have been done between 15.1-16.0)
Also have found this during LOS 16.0 debugging and when application is crashing:
Starting from Android 9, LMK can be implemented in userspace and needs new optimization settings:
Low Memory Killer Daemon | Android Open Source Project
source.android.com
Will see if this new userspace LMKD can be tuned.
@Trevor_g: can't say... I don't have an Nvidia controller to test.
Click to expand...
Click to collapse
Ok yeah i think he's right for multiple reasons
- 15.1 had still unsolved issues aside of broken omx like the crashing nv games app and not working screen mirroring which is working so far on 16.0
- 16.0 is Android 9.0 based which is the same as the actual Software for the Shield TV. That means there is maybe a chance they can use some Codes or even Apps like the Shield Accessories to makes things like the First Controller working again over WIFI.
I even found a lot Nvidia OEM Apps here on APK Mirror : https://www.apkmirror.com/apk/nvidia/
I think i start testing around with those apks as soon i installed the lasted 16.0 build
@Trevor_g
For your question i have to check that again on 16.0 with the old Controller but i think its still only working over a OTG Adapter.
Like i mentioned above maybe the Shield TV Accessories App is working.
mirhl said:
https://gist.github.com/webgeek1234/8ef1bd105d2add3aa9c29028c2befbb0
https://github.com/vartom/drivers-kernel-nvidia-49/tree/smaug49/drivers/hid
https://github.com/devmapal/nvidia-shield-controller-driver
Click to expand...
Click to collapse
Someone even mentioned this Linux Driver for the Controller
But to be honest dont suspect too much on lets say all this bonus functions because first the LOS Team have to work on the base build to make it stable and running right
Ok i installed the latest build (4/1/21) yesterday on my LTE Tablet over sideload because i had no extra SD Card to format it to FAT32 and with the new TWRP 3.5-9.0.
I installed also the Pico Gapps and then TWRP said when i was about to Restart that there's now OS installed.
But thats seems to be a bug with TWRP itself because after the restart there was the LineageOS screen waiting for me and after a freeze for about a minute or two i was able to complete my installation.
After this i now can say its the most stable LOS 9.0 Rom so far !
It has very less apps crashing so far i only had to start them twice sometimes and also the hw acceleration working now most of its time at Chrome and on the Youtube App.
I can really see there has going again a lot of work into this Rom and its really a pleasure now to see how it get more stable everytime.
Big thanks to @Steel01, @npjohnson, the whole LineageOS Team and of course to @john_matrix
Btw @john_matrix did you change anything on the partitions you mentioned earlier on this build ?
@Trevor_g
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
danielandross said:
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
Click to expand...
Click to collapse
Yes you have to wipe the device first in TWRP to install this rom.
Maybe a little general guide for everyone here who want to try this build in this early state and help tracking bugs
For an clean Installation its important to wipe the device first with TWRP like shown on the first Screenshot.
After this go to Advanced and choose everything choosen on the second Screenshot.
Now you shutdown the Tablet and insert the SD Card or plug in the cable for sideloading.
After turning on the Tablet and choose Recovery Mode again, first install the Rom of course then choose Wipe cache/dalvik.
Now you have to install Gapps if you want to use it. Its recommend to use only the Pico Package.
Wipe cache/dalvik again and restart the device.
If you use Sideload it might says in the Shutdown Menu :
No OS installed !
Which is a bug in my opinion of the new TWRP 3.5-9.0 Package but please use this Version of TWRP in any case that the basement of the installation is everywhere the same !
This is IMHO the way to install a Rom in a clean way and helps tracking down bugs better when everyone used the same methodes.
@john_matrix
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
But i have to test it a bit more side by side to make valid statements
Also Nvidia Games working nice as you can see on the Screenshots
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Scavenger87 said:
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
Click to expand...
Click to collapse
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Jackill said:
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Click to expand...
Click to collapse
In this Thread beginning from here i share my informations so far about the two type of batteries and changing them out if you interested:
Finding Replacement Battery in 2017?
Anybody know where to find a battery that will fit in the Shield Tablet? I know there are several threads online (here on xda, on GeForce forums, and other places) that discuss replacing the shield tablet battery and a few different part numbers...
forum.xda-developers.com
airtower said:
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Click to expand...
Click to collapse
I did these two type installation because @john_matrix mentioned to use a SD Card which is formated with FAT32 instead of exFAT. I didnt had one lying around so i used sideload this time.
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Seems to be going well so far for me, battery life seems good and for the general use I have had time to do it's worked well.
One crash that caused a reboot, after testing the hdmi output the tablet rebooted when I unplugged the hdmi cable from the tablet.
john_matrix said:
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Click to expand...
Click to collapse
Ok that means there is still some kind of memory leak problem with our tablets or is the memory managment on android 9 and higher not really suited for our low ram devices ?
I also read something about drawbacks with the in-kernel LMK as you can see here :
Drawbacks of in-kernel LMK driver
Android deprecates the LMK driver due to a number of issues, including:
Low-RAM devices had to be tuned aggressively, and even then would perform poorly on workloads with large file-backed active pagecache. The poor performance resulted in thrashing and no kills.
The LMK kernel driver relied on free-memory limits, with no scaling based on the memory pressure.
Because of the rigidity of the design, partners often customized the driver so that it would work on their devices.
The LMK driver hooked into the slab shrinker API, which wasn't designed for heavy operations such as searching for targets and killing them, which slowed down the vmscan process.
Is the zRam function now activated by standart on Android 9 and higher to compress amount memory is needed ?
I try to stresstest it today with a website that have a lot pictures sadly i cant use instagram anymore because you need a account now
Shield Tablet can't be considered as a "low ram device" as Google defined them with up to 512MB (Android Go?)
Android Performance Optimization | Android Open Source Project
source.android.com
I also have devices with 2GB that are currently performing Lineage 17.1 very well (Sony Z3C and Nexus 4)
I don't know if zRAM is activated by default in Android but you still have the choice to activate it or no (in the kernel or in the fstab.
Additionnally, I don't know what is the policy to activate zRAM (my Mi9 have 6GB RAM and have zRAM activated by Xiaomi so...)
Another thing about zRAM is there are lot and lot of options you can activate such as compression, lz4, clear caching, etc... depending of your needs and I am not skilled enough to say exactly what will be the consequences of these options (but it cost nothing to try).
You also have to keep in mind that zRAM will consume more CPU times (as KSM).
Similarly, you can fine tune the CPU governor and IO scheduling (often I see CFQ by default but on the other way I have saw that Noop and Deadline gives best results).
Feel free to share your experience and if you have other ideas on what you would like to integrate in this ROM (as the best possible).
You are right to stress test the OS, you can also debug the memory and the weight attributed on the processes.
Ok but 2GB is really not much these day also this article from android source is really old i think i read there something about kitkat or so
But your right i also was suprised to see that my xperia z3 compact i have lying around is able to run lineageos 17.1 and even is supported by the LOS Team
Which leads me to the question is the memory managment on the Qualcomm SOC so much better ? Ok the Ram there is on the SOC itself instead of external like on our Tegra based devices.
I think i install tonight Triodexes 15.1 with zram to compare the effect it has.
I also noticed the hw acceleration crashes the most on the firefox browser like i told in the 15.1 Thread you can start one video and it runs if you leave everything untouched but your not able to start a second one even with autoplay.
Btw about the LMK i know its maybe a dumb question but did you try the original settings from the Oem Rom ?
Edit : The original values in minfree are: 18432,23040,27648,32256,36864,46080
And zRam is already activated on the LOS 16.0 Build with 511MB same like the oem rom
Scavenger87 said:
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Click to expand...
Click to collapse
Thanks SO much for looking into this for me! You mentioned later that the controller wasn't recognized by the tablet, however I'm also curious if the Accessories app from the ShieldTV might help. Thanks again, in advance!
Fwiw, there's a bunch of framework patches needed for the wifi direct controller to work. I've yet to get them all straight. Haven't had that working since cm-12.1. See the incomplete set for 16.0 here:
https://review.lineageos.org/q/topic:shield-blake-p
That's on top of:
https://review.lineageos.org/q/topic:nvidia-shieldtech-p
And there's no nvidia pairing app that works with a touch interface. It's a mess atm. I did get blake to pair to foster on 15.1, but only while the pairing wizard was open. As soon as I hit back to close it, the autonomous group goes down and the connection is lost. And now, it's close to impossible since nvidia didn't release the nvwifi prebuilt jar to link against. And the one from O doesn't work on P.
Hi @Steel01
Thank you for keeping us updated on your work with the controller and also for your work for this device in general
I already tought its not easy to bring wifi support back for the old controller but i think also there is no high priority since the second gen is working fine over bluetooth and they already cheap to buy used.
Other than this the rom is suprisingly good running for this early stage and most of the stuff is working
Is there something that needs special attention for testing at the moment to help you developing ?
Like i mentioned in a other Thread i have every generation of the Shield Tablet and Controller. Only on my LTE Modell the SIM Card Reader is unfixable broken
But i still hunting for a fully working device.
Before I flash this Rom: Why do I habe to wipe internal storage?
danielandross said:
Before I flash this Rom: Why do I habe to wipe internal storage?
Click to expand...
Click to collapse
Well i dont know if its really needed to wipe the internal storage but i think by the reason we testing here a new Rom in a really early stage we should give it the cleanest basement as possible to exclude problems that might caused by left over data that interference with the Rom