Related
Hello, I am wondering, what are the current differences between xdandroid and neopeek for the rhodium?
Which one has better functionality? Which one has better battery life? Which one performs better and faster? And which one is more stable?
Eh those are all so subjective. Run 'em both for yourself, and draw your own conclusions.
With that said, the main difference is Neo is using cyanogenmod's stuff as the guts, and then breaking as much as he can out onto a separate ext2 partition - so his builds are a little trickier to setup, you have to partition your SD card to accomodate an ext2 partiton as well as a fat32 partition.
You can also run both versions on one card for testing. Just setup the Neo partitions first.
liveordie56 said:
Hello, I am wondering, what are the current differences between xdandroid and neopeek for the rhodium?
Which one has better functionality? Which one has better battery life? Which one performs better and faster? And which one is more stable?
Click to expand...
Click to collapse
Not sure why but neopeek's marketplace will let you download secure/encrypted market items so you will get more stuff in the market than xandroid. But with that said I always had issues with data either not working or going very slow a long with wifi issues and lots of things crashing nostop using neopeek.
Xandroid is nice and easy to setup and run... it works well but I've noticed that its a bit slow for me. Usually the items that work (wifi, bt, audio, ect...) typically work first on xandroid then become available within a week or so on Neopeek roms.
Neopeek is a bit trickier to set up and requires the ext2 partition that everyone before me mentioned. Once you do it once though, its pretty straight forward to use. There are several builds of neopeek roms (Superfroyo, Froyoredux, CM6 mods, ect) In my experience, Neopeek roms are more stable and have somewhat better battery life (especially the latest superfroyo).
From my experience, the same kinds of glitches show in both, data randomly not working, in call volume issues, low signal (or at least poor signal indication), the phone radio getting glitched, ect.
On neopeek builds, I have noticed that some roms have never ending android process crashes and random reboots. I have noticed that formatting the ext2 partition and then running mkfs.ext2 /dev/SDCardIdentifier seems to be a good idea when switching builds of a rom and seems to alleviate this issue. The latest version of SuperFroyo is working awesome, I have not had a single crash or anything.
Also, frequently updated is the glemsom builds of kernel and module files (found in a link below). These also may change your stability/functionality. for example. in the latest build of SuperFroyo (the build i typically hold my breath for) I could not get past the initial device setup (Android setup wizard) updating the kernel to the one that was latest at the time fixed my issue.
Also, Neopeek wireless for Rhodium is not necessarily finished although I have found a fix for it which I will post in a new thread for everyone to find.
Overall, Neopeek I Choose You!
Glesmom Link : http://glemsom.users.anapnea.net/android2/htc-msm-linux/
RickoT said:
Xandroid is nice and easy to setup and run... it works well but I've noticed that its a bit slow for me. Usually the items that work (wifi, bt, audio, ect...) typically work first on xandroid then become available within a week or so on Neopeek roms.
Neopeek is a bit trickier to set up and requires the ext2 partition that everyone before me mentioned. Once you do it once though, its pretty straight forward to use. There are several builds of neopeek roms (Superfroyo, Froyoredux, CM6 mods, ect) In my experience, Neopeek roms are more stable and have somewhat better battery life (especially the latest superfroyo).
From my experience, the same kinds of glitches show in both, data randomly not working, in call volume issues, low signal (or at least poor signal indication), the phone radio getting glitched, ect.
On neopeek builds, I have noticed that some roms have never ending android process crashes and random reboots. I have noticed that formatting the ext2 partition and then running mkfs.ext2 /dev/SDCardIdentifier seems to be a good idea when switching builds of a rom and seems to alleviate this issue. The latest version of SuperFroyo is working awesome, I have not had a single crash or anything.
Also, frequently updated is the glemsom builds of kernel and module files (found in a link below). These also may change your stability/functionality. for example. in the latest build of SuperFroyo (the build i typically hold my breath for) I could not get past the initial device setup (Android setup wizard) updating the kernel to the one that was latest at the time fixed my issue.
Also, Neopeek wireless for Rhodium is not necessarily finished although I have found a fix for it which I will post in a new thread for everyone to find.
Overall, Neopeek I Choose You!
Glesmom Link : http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Click to expand...
Click to collapse
okay, thanks i think i have decided to go with the neopeek build's i have a question for you though, on the latest SuperF build (on neopeek's forum October 8, 2010) My data stops working after a call. did you run across this problem? I updated to the latest kernel too and it still did not fix the problem.
Are you on edge? That would disconnect data during a call... it should reconnect though when you are done
hmm it says 3g on android, but when i end the call and my friend tries to call again, it never reaches, and when i try to call, there's no ringing or anything, along with that, when i press hang up, it is stuck on "hanging up".
Yah I get that too sometimes (on xandroid and neopeek) I think its more of a general radio driver issue/radio image than the build honestly... dont forget that this radio was meant to be used with windows mobile not android.
ahhhhh, okay thanks for the information
wondering?
Is there any progress on a camera fix yet?
There will be fanfare and confetti all over the forums when camera works.
Seriously, you will know when it's working. It's not yet.
camera .. yuck..
After some water exposal, bottom hardware buttons (along with optical trackball) refused to work.
I have fixed them with some precise inside cleaning, but the optical function (not the button himself) continues malfunctioning, which is not a big deal for me, but..
The exact problem: i spotted in dark environment, that the sensor inside continuously glimmers in all modes - scren-off, scren-on (without puting finger over him), etc.. In return, my battery drains extra aprox. 10-12 mA!
I have observed, that in healthy device, sessor glimms only when interacting with him..
Is there a chance to disable this sensor to avoid this? I hope in software manner
I don't think there is anything out there that will disable the optical pad. You could give HTC a call or your carrier and see what they say.
There is this thread on the forums about turning off the backlights.
Should work for trackball as well? Probably. Something about LED Hack on the first or second page. Seems to be something on the 3rd page as well.
Go have a read over here (I just skimmed. its 2am lol) http://forum.xda-developers.com/showthread.php?t=704977
@formformer
If you tell me your kernel version I will try to build a kernel without trackpad support!?
@Meaple 's post was sadly adequate and rips best hope in me ;( ..
@eden2812 I have using 2 led hacks from previous attempts to minimize energy consumption & eye comfort, and they shurely don't do the "trackpad sensor shutting" job..
@AndroidJaspie
it's so damn cool to offer this kind of experience. salute!
i have likely using latest Ginger Villain's compilation, but any recent rom-kernel set, with weak appetite fits my best.
i will be very patient to hear from you..
my current setup is:
OK I built a new kernel from the cyanogenmod sources now without trackball support. I tested it with GingerVillain 1.4 and it worked.
please make a backup and then give the update.zip a try.
Tell me if the new kernel solved your problem or not.
Jasper
Yes Jasper, obviously the sensor is shutted (no glimmering observes) and the xtra drain is all gone now!! I'm so pleased.
But i have found, that the bottom buttons (including the button under the optical trackpad) not waking the phone any more. Is this issue related?
And another, not so important question: Would be this kernel compliant with other Gingerbread releases? or.. could you give me some hint, if is possible to transform your "surgery" into a some kind of a patch, that will give me opportunity to enjoy any feature kernel/roms?
Again, BIG 10x for your respond in this custom problem so far! You make my life happier
karel
No problem i like it to work with things like that. So it's a good chance to improve my knowledge about linux and help other people at the same time.
Are you talking about the all buttons or only about the button around the optical sensor?
If you are talking about the one around the sensor then it's normal that it won't wake up the phone any more. But the others(home, menu, back and search) should work like before.
This kernel works only with cyanogenmod and GingerVillain. On other rom's like Oxygen it doesn't work. But you i can compile you the kernel you want.
At the moment it's only possible to disable the trackball only by editing the kernel configuration. But i will try to get it working without changing the kernel so that you can use every kernel you want.
Jasper
i told so, about the relation of shutted sensor and not working buton.., but yes, others buttons also not working in lockscreen-off mode, where they should or at least worked before. (volume butts still works for wakening..)
ps. a have barely no linux skills, but its interesting for me either!
and if editing & compiling is not so high level task, im going to try first steps right now!
Any way, disabling track sensor without editing kernel settings sounds like a dream..
k
hi, my fried
could you tell me, where in the config I can find the exact setting and how to change it?
hi
if you got the kernel source you can make menuconfig to configure the new kernel. To disable the trackball go to "Device Drivers" --> "Input device support" --> "Opticaljoystick". To disable the joystick press "n" to enable it press "y"
Don't know how to comile your own kernel?
here is a useful links that helped me, too:
-[HOW-TO] Build your own kernel package from source
huh.. 10x 4 the guides, they light me enough to get started week ago, but i get stuck just in the beginning (problems with MBR or something..). and at this moment i have absolute lack of time to deal with this interesting stuff. However.. can i have one more last ask from you: to compile for me an updated kernel.. (they says he has the ability to record 2way call conversations..)
Using the Ginger Villain rom, suppose with this richardtrip kernel. Guess CM will worx too..
Thanks anyway!
ok
a bit late but here it is
a new kernel version 2.6.37.2 from the richardtrip-sources.
kernel features:
-disabled trackball
I don't know anything about "Two-way call recording kernel support" but i will try to find out as much as posible to configure a kernel with it.
jasper
Hi AndroidJaspie, i've the same problem with the optical trackball of my desire. I use the miui rom with the kernel 2.6.37.6-cyanogenmod-g8913be8. Can i use the kernel in your last post? thx bye
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Please stay ON TOPIC to kernel DEV and missing code. Don't report every bug the Android build your using is having or it will be deleted as OFF TOPIC
As you all might be knowing that hd2 is pretty much a android native device now. Its just like any another snapdragon device. The current kernel code we are using in HD2 is pretty obsolete and missing a lot of things. It more like something working at its minimal efficiency. While i was porting over all the HD2 board files getting it on par with the other snapdragon devices I found out a lot of code was missing and some was obsolete. Eg. The gsensor code from microp was pretty minimal, a lot of things were missing in microp code. I suspect that it isnt the only code, a lot of bluetooth related stuff was missing and much more. I am not really gonna work on backporting the stuff to .32 kernel so i would like the kernel devs here to backport the stuff to the .32 kernel so a lot of bugs can be fixed and stuff can be made more stable until the .37 kernel is ready. All the commits can be found here
https://github.com/charansingh/cm-kernel/tree/master
There might be some bravo or passion instances in there cuz i am comparing the code with these two devices and taking what is necessary and sometimes i have to leave my work due to some other work and forget which file i was working on so would appreciate the more bugs.
Also Mods can we get this a sticky so we can track the progress here
Yap.. i'm not a really pro developer but i suspected those bugs before.. finally a real developer suspected that.. eager to see who's going to help fixing them
charnsingh_online said:
Also Mods can we get this a sticky so we can track the progress here
Click to expand...
Click to collapse
Ok sticky for the moment to see if it helps.
@charnsingh_online
I am really happy that you put so much power in this project big respect for that.
The reason for the missing code is because most of the drivers are reversed engineerd from winmo by cotulla. Wich make it possible to make working android parts but they don't work optimal by that. Also we miss some skilled active coders. After cotulla almost everything is created by markinus he did a incredible part big credit to him but looks like he isn't that active anymore..
Current development are mostly little things a guy who sees a little part from that and a little part from that like : you, tytung, darkstone, gauner,letama, the guy from the bluetooth fix.
We probaly don't have so much real kernel programmers because they buy a native linux / android phone.
The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252
memin1857 said:
The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252
Click to expand...
Click to collapse
actually i think the gpu drivers are kinda unstable when comparing to the performance of other phones that carry the similar gpu...
@charnsingh_online
Good start.
After reading the github commits, I still don't understand what kernel devs can do so far.
Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code
hi charansingh,
i am willing to help, but i think it would be helpfull to define packets to take over.
By looking in the kernelsources it looks good to me, but i know from own expiriences with porting that i have to look deep...
best regards
trilu
charnsingh_online said:
Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code
Click to expand...
Click to collapse
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.
Ok I'll do it tomorrow n also maintain the list in the op
I may be wrong, but this thread is not supposed to become a bug fix request thread. It is aimed at developpers, so that they collaborate on a merging of HD2 specific stuff onto a cyanogen 2.6.37 kernel...
This would most likely result in the resolution of a lot of our issues, but in the mean time, [DEV] in the thread title means it is for devs only......
Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.
I looked pushed code and it's ok, at least for first few commits. But it needs some deep cleaning an optimization, also there is some bravo naming convention used in leo specific files. You should put this tree on gitorious so we can do more work on it, but anyway i will clone tree and do some cleaning and porting new stuff.
This could be of interest, and not too much off-topic.
This kernel: http://forum.xda-developers.com/showthread.php?t=966786
is being abandoned and it had some patches for performance that I think are valuable. It had linpack scores that can be achieved only with heavy overclocks on other kernels... The problem is, the source is being distributed by a .zip, no commits, nothing... the only way to get those would be to issue a diff with... something and guess where they are. Staying on topic, I've already adapted cm-kernel for another device so I think I'll be able to help when I get enough free time to spare.
D4rk50ul said:
Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.
Click to expand...
Click to collapse
Yes you are right. Unfortunately many threads like this one get's filled with off topic chatter, complaints etc. I will try to keep my eye on this thread so the dev's can communicate. If your not contributing to the DEV work on the HD2 kernel's, please don't post your wishes and thanks post as this will quickly clog up the thread. I'd hate to lose progress due to this. That's why many DEV's end up not using XDA and reverting to IRC only. Thanks
noellenchris
Hi,
Few days back there are some conversation about libsurfaceflinger.so for color banding issue http://forum.xda-developers.com/showthread.php?t=1012278 . Since Rom is changing continuesly with libs can we port the change for color issue.
HD2 GB-2.33-SENSE-2.1 LOCKSCREEN SENSE-3
tytung said:
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.
Click to expand...
Click to collapse
tytung, has any1 of you done so? please let us know..
g30rg10u said:
tytung, has any1 of you done so? please let us know..
Click to expand...
Click to collapse
No, I didn't work on 2.6.37 kernel so far.
I didn't see that charnsingh_online added a TODO list in the OP.
Fried my laptop charger. New one on way. Hd2 arrived
--update4 feb 18 below: camera patch + WIFI dropped connection
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
--update1 (new user = no new post to devel board):
Thanks arrrghhh for moving my post here. Yes, the zip can be flashed from SD card from the boot menu.
[ACL], the changes apply to all MACH_TYPE_HTCRHODIUM machines (from mach-types.h), that includes all GSM Rhodium devices I believe. I don't know how to narrow that down to the 100 alone, aside from using a kernel boot parameter.
As for the intended scope for this change: most people reporting camera issues are rhod100 users, but I've seen posts from non-rhod100 users having occasional camera crashes. Because the patch targets the used frame rate it is likely that the camera hardware in most rhod100s - and some non-100's? - just can't handle the original framerate. So if there are non-rhod100 users having occasional camera crashes...
--update2
Changed patch to make it rhod100 specific using machine_variant_type. Thanks muziling. See attached zip and diff (postfixed _1). Non-rhod100 users with crashing camera's -if any- should use the original zip to test.
Please note that this patch does not include brinka123's change for low-light conditions. Didn't that one cause problems when zooming in? I can look into that change, but would like to separate it from this patch.
Next thing I want to do is look into the audio issue when using the cam - audio runs for 1 sec, then drops. I need to go into Android code for that*
I've worked hard this evening to compile OMGB with [ACL]'s device specific files (both github), but failed miserably. Looks like I'm missing the rhodium makefiles, any pointers?
I did manage to get 7.5 GB of sources on my PC, so I guess I'm at least halfway
*: while recording video logcat shows a happily recording cam and then suddenly:
V/Libacoustic-wince( 85): msm72xx_start_acoustic_setting
I/AudioHardwareMSM72XX_wince( 85): disabling volume method=AUDIO
V/Libacoustic-wince( 85): msm72xx_set_acoustic_table 256 0
V/Libacoustic-wince( 85): Use current device 13
-- update3
The attachment OMGB_2.6.27.46-01399-g6a073c7-rhod100camera_1.zip lacked matching kernel modules (no wifi, ...).
Corrected that by uploading attachment OMGB_2.6.27.46-01399-g6a073c7-rhod100camera_1a.zip
Note that this second update does nothing for rhod 2xx,3xx devices.
--update4
Camera:
Some people reported improved all-rhodium camera quality under low-light conditions using brinka123's changes. The change that is present in the attached patch does improve low-light image quality somewhat as it lowers the framerate, increasing the ccd integration time (1 frame + blanking). The remaining changes from brinka123 not included in the patch do not improve low-light image quality. These changes just limit the CCD integration time to one frame incl blanking, preventing hardware enforced framerate drop but delivering a darker picture with more noise. So I think the patch as-is is fine.
Wifi:
To properly debug camera audio issues I wanted a build environment using OMGB git + [ACL]'s device_htc_rhodium git. After a week of total war between me and the Android build system I have a working environment that results in a working phone. Had to create lots of Android makefiles from scratch to do that, and by accident it resulted in a phone that doesn't drop it's WIFI connection every now and then (Wifi icon turned gray 1-2 times a day, toggling wifi off/on reconnects). The difference with [ACL]'s build is not in the code, but somewhere in the makefiles + properties + different firmware files and is difficult to narrow down. If the WiFi issue I had is real and not something limited to my phone/access points I can look into this. Anyone with this problem?
Thanks mate, moved your thread to development.
Interested to hear how this pans out. I'm assuming RHOD100 users on OMGB can just flash that .zip via recovery?
ImTuxy said:
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
Click to expand...
Click to collapse
Hey dood. Lets get some rhod 100 folk to test this bad boy. We also need to make sure it doesnt break the other variants. I'm also going to send this to the kernel team so it can be analyzed for xdandroid as well. If this change is Rhod100 specific, then we need to change it so only rhod100 loads it.
ImTuxy said:
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
Click to expand...
Click to collapse
Great work, Eric. I have tested now cursorily and first observations are:
1. Camera works great including autofocus
2. Camcorder - videorecording works, but there is problem with recording audio. Recording approximately first 1 second and then silence.
I made 4 photos and 2 videos (30 second and 5 second) and this consumed 49% of my battery.
May I send you any logs or another help with testing?
Anyway many, many thanks to you!
Edit: After recording this kernel is sometimes spontaneously turns on the display including four buttons at bottom, in that moment the LED lights up in orange (wake) and immediately off again and the LED turns green (sleep). Display lights approx. 1 second.
[ACL] said:
Hey dood. Lets get some rhod 100 folk to test this bad boy. We also need to make sure it doesnt break the other variants. I'm also going to send this to the kernel team so it can be analyzed for xdandroid as well. If this change is Rhod100 specific, then we need to change it so only rhod100 loads it.
Click to expand...
Click to collapse
I was under the impression that the 'improvements' would actually help all RHOD's. I know when I ran brinka's kernel for testing, the low-light performance did seem better.
So unless it outright breaks all other RHOD's, I'd say it should be applied to all RHOD's.
milda25 said:
Great work, Eric. I have tested now cursorily and first observations are:
1. Camera works great including autofocus
2. Camcorder - videorecording works, but there is problem with recording audio. Recording approximately first 1 second and then silence.
I made 4 photos and 2 videos (30 second and 5 second) and this consumed 49% of my battery.
May I send you any logs or another help with testing?
Anyway many, many thanks to you!
Edit: After recording this kernel is sometimes spontaneously turns on the display including four buttons at bottom, in that moment the LED lights up in orange (wake) and immediately off again and the LED turns green (sleep). Display lights approx. 1 second.
Click to expand...
Click to collapse
This patch does absolutely nothing for recording audio. I would ask how it worked before, but you've probably never been able to test it.
So long as it fixes the cam, we're good. Recording/audio is completely separate from this patch.
arrrghhh said:
I was under the impression that the 'improvements' would actually help all RHOD's. I know when I ran brinka's kernel for testing, the low-light performance did seem better.
So unless it outright breaks all other RHOD's, I'd say it should be applied to all RHOD's.
This patch does absolutely nothing for recording audio. I would ask how it worked before, but you've probably never been able to test it.
Click to expand...
Click to collapse
Sorry, I did not know this. Before the camera really did not work at all. There is tremendous progress. Thanks.
Tested on Rhod100.
milda25 said:
Sorry, I did not know this. Before the camera really did not work at all. There is tremendous progress. Thanks.
Tested on Rhod100.
Click to expand...
Click to collapse
Yes, it is nice to have the cam working at all, and I realize you couldn't test this before.
I just wanted to make that clear, this will only fix the broken cam. Nothing else...
Both RHOD100,210,300 user had crash
Use function get_machine_variant_type to get rhod type, it will return
MACHINE_VARIANT_RHOD_1XX or MACHINE_VARIANT_RHOD_2XX, MACHINE_VARIANT_RHOD_3XX,MACHINE_VARIANT_RHOD_4XX,MACHINE_VARIANT_RHOD_5XX
muziling said:
Both RHOD100,210,300 user had crash
Use function get_machine_variant_type to get rhod type, it will return
MACHINE_VARIANT_RHOD_1XX or MACHINE_VARIANT_RHOD_2XX, MACHINE_VARIANT_RHOD_3XX,MACHINE_VARIANT_RHOD_4XX,MACHINE_VARIANT_RHOD_5XX
Click to expand...
Click to collapse
Exactly !!!
here is some pseudo to brighten everyones day
Code:
current_variant = get_machine_variant_type();
if ((current_variant == MACHINE_VARIANT_RHOD_1XX)) {
do_rhod100_poop();
}
ImTuxy said:
--update2 feb 08 below
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
--update1 (new user = no new post to devel board):
Thanks arrrghhh for moving my post here. Yes, the zip can be flashed from SD card from the boot menu.
[ACL], the changes apply to all MACH_TYPE_HTCRHODIUM machines (from mach-types.h), that includes all GSM Rhodium devices I believe. I don't know how to narrow that down to the 100 alone, aside from using a kernel boot parameter.
As for the intended scope for this change: most people reporting camera issues are rhod100 users, but I've seen posts from non-rhod100 users having occasional camera crashes. Because the patch targets the used frame rate it is likely that the camera hardware in most rhod100s - and some non-100's? - just can't handle the original framerate. So if there are non-rhod100 users having occasional camera crashes...
--update2
Changed patch to make it rhod100 specific using machine_variant_type. Thanks muziling. See attached zip and diff (postfixed _1). Non-rhod100 users with crashing camera's -if any- should use the original zip to test.
Please note that this patch does not include brinka123's change for low-light conditions. Didn't that one cause problems when zooming in? I can look into that change, but would like to separate it from this patch.
Next thing I want to do is look into the audio issue when using the cam - audio runs for 1 sec, then drops. I need to go into Android code for that*
I've worked hard this evening to compile OMGB with [ACL]'s device specific files (both github), but failed miserably. Looks like I'm missing the rhodium makefiles, any pointers?
I did manage to get 7.5 GB of sources on my PC, so I guess I'm at least halfway
*: while recording video logcat shows a happily recording cam and then suddenly:
V/Libacoustic-wince( 85): msm72xx_start_acoustic_setting
I/AudioHardwareMSM72XX_wince( 85): disabling volume method=AUDIO
V/Libacoustic-wince( 85): msm72xx_set_acoustic_table 256 0
V/Libacoustic-wince( 85): Use current device 13
Click to expand...
Click to collapse
we share acoustic and libaudio with xdandroid. Just compile it there and move the binaries over. Detule is the master of these for now and he has been killing bugs left and right.
Also your second patch looks worthy. So next round of updates i'm going to include it.
We are tracking this issue on the issues list.
http://code.google.com/p/rhodium-nand/issues/detail?id=15
You can update the request if you have more info.
Long time lurker, first time poster (which means I can't post in the actual ROM thread). If my thread is inappropriate, please feel free to revise/delete as necessary. If additional information is needed from me, please advise.
By way of background: I have experience with flashing on this phone dating back to Gingerbread with IncredibleHD and MikRunny from "another site". I came over from a Samsung Fascinate where I was also flashing ROMs. So while not an expert in the actual development of the device, I would like to think I am somewhat experienced with flashing ROMs at least.
Incredibly(^<Paranoid2.19.30Final Questions:
With my current flash of Incredibly(^<Paranoid2.19.30Final, I am not running any themes and installation should be basically standard (though I did have to flash the October GApps package over it because there was no way to set up a Google account).
1. Aroma: The Revised OP still talks about the Aroma installer (I know that there have been two versions of the ROM zip in the past). When I flashed 2.19.30, there was no Aroma installer. Bad download or mistake in OP? Answered in Post #4.
2. Camcorder: Regular camera and FFC are working correctly. The OP says that the camcorder has 720p enabled at this point. However, I do not see anywhere in the settings to change the quality of the camcorder, and the camcorder is currently recording at 480p. How do I change the camcorder to 720p? Answered by The Man himself in Post #14.
3. Bluetooth in Car: With the various AOSP ROMs, when connecting the phone to my car via Bluetooth (not A2DP, just a headset profile), I get sound but it is garbled beyond belief while ringing. For any music buffs, the sound is basically the first chord of "I Believe In a Thing Called Love" by The Darkness...as the sound of a phone ringing. Per Rushead's post #710, it appears that Bluetooth headsets and in-call voice are not functional, which is a known issue in AOSP ROMs under ICS and JB with no fix. Has this been resolved in this ROM since "everything" works but LED camera flash? Answered in Post #9 via OP for Incredibly(^<Paranoid Collection.
4. Status Bar Clock: I want to eliminate the clock in the status bar. I go in to the AOKP settings via Settings > ROM Control > Clock > Clock Style and select "No Clock". This removes the clock from the status bar. However, when the phone goes to sleep, and I come back through the lock screen, the clock is back. Going back in to the settings as referenced above, the "No Clock" option is still selected...and yet there is a clock there. If my memory serves me, in Aeroevan's CM10 the option would be under Settings > System > Status Bar, but there is no option for the clock there in Incredibly(^<Paranoid. Obviously not a huge deal, but just curious if anyone has a suggestion. Answered in Post #9; works fine in CM10 so who cares.
Any information or assistance would be greatly appreciated.
VenomINC 1.3.1 Question:
While my primary questions are related to Incredibly(^<Paranoid as I am digging JB at the moment, as I am already running up my technical support bill I figure I will ask a VenomINC question as well.
I have tried the various Sense-based ROMs under ICS (but VenomINC in particular...same thing, standard install, no themes) and have a giant issue that does not seem to have popped up in that thread: everything works perfectly, with one exception: no audio comes out of the headphone jack. I have tried an aux cable in the car, regular headphones...nothing. This makes the Sense ROMs unusable for me personally, as I spend a good amount of time in the car for work and listen to podcasts/music.
As best I can tell, I believe that this only happens with Sense 4 based ROMs (UKB, ViperINC, EclipticSense over on "another site") but not with Sense 3.6 ROMs (Ascension, the Nitsuj ICS leak) or with CM based ROMs (including Aero's CM10). I will note that I have not tried changing the kernel - I understand that Viper is using the Chinese kernel, while some of the other ROMs have the leak kernel.
The issue was raised in the ViperINC thread by user artcotto in post #s 615, 634, 689, 691, and 693 with no resolution beyond Nitsua98 helpfully suggesting that maybe his headphones were broken (they were not). I have flashed the various updates to ViperINC since November and the issue has not gone away. Any information on this would be appreciated as well as I am a bit of a flashoholic and would likely go back and forth between Sense and AOSP (even though as noted above JB is pretty awesome).
Thank you for the great community and for any information and assistance you can provide. Thanks to all the developers for all the hard work you have done for our phone (which was apparently ancient and incapable of upgrade by HTC the second we bought it) allowing me to have a current phone without needing to buy a NEW phone.
Re: ViperInc headphones
VenomINC 1.3.1 Question:
While my primary questions are related to Incredibly(^<Paranoid as I am digging JB at the moment, as I am already running up my technical support bill I figure I will ask a VenomINC question as well.
I have tried the various Sense-based ROMs under ICS (but VenomINC in particular...same thing, standard install, no themes) and have a giant issue that does not seem to have popped up in that thread: everything works perfectly, with one exception: no audio comes out of the headphone jack. I have tried an aux cable in the car, regular headphones...nothing. This makes the Sense ROMs unusable for me personally, as I spend a good amount of time in the car for work and listen to podcasts/music.
As best I can tell, I believe that this only happens with Sense 4 based ROMs (UKB, ViperINC, EclipticSense over on "another site") but not with Sense 3.6 ROMs (Ascension, the Nitsuj ICS leak) or with CM based ROMs (including Aero's CM10). I will note that I have not tried changing the kernel - I understand that Viper is using the Chinese kernel, while some of the other ROMs have the leak kernel.
The issue was raised in the ViperINC thread by user artcotto in post #s 615, 634, 689, 691, and 693 with no resolution beyond Nitsua98 suggesting that maybe his headphones were broken (they were not). I have flashed the various updates to ViperINC since November and the issue has not gone away. Any information on this would be appreciated as well as I am a bit of a flashoholic and would likely go back and forth between Sense and AOSP (even though as noted above JB is pretty awesome).
Thank you for the great community and for any information and assistance you can provide. Thanks to all the developers for all the hard work you have done for our phone (which was apparently ancient and incapable of upgrade by HTC the second we bought it) allowing me to have a current phone without needing to buy a NEW phone.[/SIZE]
Click to expand...
Click to collapse
great questions. i am in the same situation...a little experience but not enough forum-cred to post in dev.
i'm currently running ViperInc 1.3.1, just plugged in my el-cheapo RCA headphones and they work fine. sorry bro :-/
i'd love to see some answers to your 2.19.30 questions.
johannvonperfect said:
Long time lurker, first time poster (which means I can't post in the actual ROM thread). If my thread is inappropriate, please feel free to revise/delete as necessary. If additional information is needed from me, please advise.
By way of background: I have experience with flashing on this phone dating back to Gingerbread with IncredibleHD and MikRunny from "another site". I came over from a Samsung Fascinate where I was also flashing ROMs. So while not an expert in the actual development of the device, I would like to think I am somewhat experienced with flashing ROMs at least.
VenomINC 1.3.1 Question:
While my primary questions are related to Incredibly(^<Paranoid as I am digging JB at the moment, as I am already running up my technical support bill I figure I will ask a VenomINC question as well.
I have tried the various Sense-based ROMs under ICS (but VenomINC in particular...same thing, standard install, no themes) and have a giant issue that does not seem to have popped up in that thread: everything works perfectly, with one exception: no audio comes out of the headphone jack. I have tried an aux cable in the car, regular headphones...nothing. This makes the Sense ROMs unusable for me personally, as I spend a good amount of time in the car for work and listen to podcasts/music.
As best I can tell, I believe that this only happens with Sense 4 based ROMs (UKB, ViperINC, EclipticSense over on "another site") but not with Sense 3.6 ROMs (Ascension, the Nitsuj ICS leak) or with CM based ROMs (including Aero's CM10). I will note that I have not tried changing the kernel - I understand that Viper is using the Chinese kernel, while some of the other ROMs have the leak kernel.
The issue was raised in the ViperINC thread by user artcotto in post #s 615, 634, 689, 691, and 693 with no resolution beyond Nitsua98 suggesting that maybe his headphones were broken (they were not). I have flashed the various updates to ViperINC since November and the issue has not gone away. Any information on this would be appreciated as well as I am a bit of a flashoholic and would likely go back and forth between Sense and AOSP (even though as noted above JB is pretty awesome).
Thank you for the great community and for any information and assistance you can provide. Thanks to all the developers for all the hard work you have done for our phone (which was apparently ancient and incapable of upgrade by HTC the second we bought it) allowing me to have a current phone without needing to buy a NEW phone.
Click to expand...
Click to collapse
Have you tried earlier versions of ViperInc? I am using 1.0.2 and have none of the issues I was having with 1.3.1 (which were not your issues - just lag). Another question would be - and I'm not sure this would really affect the jack - have you flashed the firmware?
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
Question number 1: that was a kind of op misunderstanding, a previous version included aroma, while the best one does not, your download was fine
Sent from my Incredible 2 using xda app-developers app
brymaster5000 said:
Have you tried earlier versions of ViperInc? I am using 1.0.2 and have none of the issues I was having with 1.3.1 (which were not your issues - just lag). Another question would be - and I'm not sure this would really affect the jack - have you flashed the firmware?
Click to expand...
Click to collapse
I have not tried going back to prior versions of ViperINC, though I believe I have used from 1.1 onward and had this issue. I didn't mention in my original post, but yes, I have flashed the ICS firmware with the 0320 radio. Maybe 1.0.2 would be worth a try (though I'm not sure there is a way to get old versions of the ROM).
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
This might sound odd. I've been on viper the longest. No lag. I installed super su n un installed their SU. Also got a busy box installer from the market n updated the phones busy box. I'm also running defensed but made sure I popped in rosie, but it's frozen n I'm running nova. Night n day I tell ya.
Sent from my forgotten by HTC Droid Incredible 2. Rooted and Rommed by great minds that haven't forgotten this phone.
johannvonperfect said:
I have not tried going back to prior versions of ViperINC, though I believe I have used from 1.1 onward and had this issue. I didn't mention in my original post, but yes, I have flashed the ICS firmware with the 0320 radio. Maybe 1.0.2 would be worth a try (though I'm not sure there is a way to get old versions of the ROM).
Click to expand...
Click to collapse
fwiw, i also have 0320 radio with headphones working fine. i was previously on ViperInc 1.2.0 and EclipticSense and it also worked fine.
Can you think of anything else you did with your phone around the time you first started experiencing the headphone issue?
vikrantislav said:
fwiw, i also have 0320 radio with headphones working fine. i was previously on ViperInc 1.2.0 and EclipticSense and it also worked fine.
Can you think of anything else you did with your phone around the time you first started experiencing the headphone issue?
Click to expand...
Click to collapse
Not that I'm aware of. As I mentioned above, I don't think it's a "hardware" issue, in the sense that even now I have no problems with CM 10, Incredibly(^<Paranoid2.19.30, etc. My best thought was that it may be something with the way the Sense 4 ROMs interact with the hardware, i.e. maybe the kernel on my particular phone? But I have no idea. At some point I will try flashing the "leak" kernel over the VenomINC install.
What I'm more interested in at this point is 720p recording on Incredibly(^<Paranoid2.19.30Final (And I am looking forward to Chilly throwing together a CM10 ROM).
If we keep going back and forth we can rack up enough posts to start posting at the grown-up table :good:
So the revised OP for what is now the Incredibly(^<Paranoid Collection answered a couple of the questions.
Bluetooth phone calls do not work in any of Chilly's ROMs.
I flashed his CM10, and the issue with the clock in the status bar is resolved. This leads me to believe it is an AOKP/PA issue; I am fine with CM10 anyway so no big deal there.
However, when I flashed CM10, the same issue exists with the camcorder. FFC and regular camera work great for photos; there is no option to change the camcorder to 720p.
Re: ViperINC issue: I flashed ViperINC 1.3.1 again, and this time I flashed the "leak" kernel over it. Still no audio through the headphones. I tried turning Beats Audio on/off, did not do anything.
Only issues I have with Viper is it will not connect to my media server via the native apps. I also have been experiencing lag but I think it's mainly due to lack of ram as a reboot usually clears it up. Also if you toggle gps off it doesn't work unless you reboot.
johannvonperfect said:
Re: ViperINC issue: I flashed ViperINC 1.3.1 again, and this time I flashed the "leak" kernel over it. Still no audio through the headphones. I tried turning Beats Audio on/off, did not do anything.
Click to expand...
Click to collapse
that reminds me, i also have the Sony XLoud disabled in ViperINC
vikrantislav said:
that reminds me, i also have the Sony XLoud disabled in ViperINC
Click to expand...
Click to collapse
I did not install XLoud in the Viper Installer, just went with Beats. As I said in the OP, I know that my issue was previously mentioned but it does not seem like anybody ever found out the cause.
Bluetooth phone calls are not a dealbreaker for me. At this point, if the 720p recording is actually working, I would be happy with CM10 as a daily driver (though I may check out Evervolv as well to see what 4.2 can do). I just can't find the setting...
So what I think I pieced together: the Chilly collection of ROMs does not have 720p recording. When he was talking about the camera being fixed 99.999% except for flash, he was talking about FFC only, and the ROMs do not have 720p recording. I am hoping I am wrong but confirmation would be appreciated.
It may be a situation like the DKStunna thread, where it was proudly proclaimed at the top that "EVERYTHING WORKS", except for the stuff that didn't that you were just supposed to know hadn't been fixed. When Chilly said in Post #875 that "Lol FFC can works ..led flash works but not with taking pictures...video etc works" that does not appear to mean that 720p recording works.
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
johannvonperfect said:
So what I think I pieced together: the Chilly collection of ROMs does not have 720p recording. When he was talking about the camera being fixed 99.999% except for flash, he was talking about FFC only, and the ROMs do not have 720p recording. I am hoping I am wrong but confirmation would be appreciated.
It may be a situation like the DKStunna thread, where it was proudly proclaimed at the top that "EVERYTHING WORKS", except for the stuff that didn't that you were just supposed to know hadn't been fixed. When Chilly said in Post #875 that "Lol FFC can works ..led flash works but not with taking pictures...video etc works" that does not appear to mean that 720p recording works.
Click to expand...
Click to collapse
I had got 720p working but it caused problems so I removed it u caught the thread before the revamp
Currently working on most my roms is
FFC with recording
Tethering with 3party app
I will be implementing fixes for led flash
Blue tooth works but has some bugs
Mostly everything works with fixes that I will be implementing
The pa I upped has fixes already baked in ..I'm yet to try BT yet
Once fixes have been baked the roms will be fully functional minus 720p
Sent from my Incredible 2 using xda app-developers app
chillybean said:
I had got 720p working but it caused problems so I removed it u caught the thread before the revamp
Currently working on most my roms is
FFC with recording
Tethering with 3party app
I will be implementing fixes for led flash
Blue tooth works but has some bugs
Mostly everything works with fixes that I will be implementing
The pa I upped has fixes already baked in ..I'm yet to try BT yet
Once fixes have been baked the roms will be fully functional minus 720p
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
That must have been what happened...I have kept up with the thread fairly regularly and thought I saw that 720p had been figured out, but as you said that must have been before it was pulled. I was confused why nobody was mentioning it in the thread considering it would have been big news.
Chilly, thanks for the response, and thanks for all the hard work you do to make the phone feel like new. We're lucky to have such talented devs keeping our device relevant. Keep doing what you do! :highfive:
To the Mods: that should wrap up this thread if you want to lock it. I do not believe there is an answer to my remaining question about ViperINC and audio through the headphone jack.
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
Hehe even the mods have moved on...
Once everyone leaves this device Verizon will update it like the thunderbolt.
Sent from my Nitsy CM7.
I don't think it was mentioned, but did you try a reflash / redownload?
Probably not going to do anything, but worth a shot.
brymaster5000 said:
Hehe even the mods have moved on...
Once everyone leaves this device Verizon will update it like the thunderbolt.
Sent from my Nitsy CM7.
Click to expand...
Click to collapse
Sweet. I'm locked in my phone till November so I'll be like 1 outta 12 people left with the phone rocking ICS. Sounds exciting
Can usb tethering be done in cm10. I saw the WiFi app thread but nothing on usb.
Not to bump an old thread, but since I still can't post in the actual development thread: Chilly said in Post #1369 of his ROM thread that "No such thing as 100% but yes everything should work other then rotating hard keys bust out the champagne!"
Therefore my question is, once again: how do you change video recording quality to 720p in the camcorder? There still doesn't seem to be an option for it. Any info would be appreciated.