[TESTING] - NAND OMGB (1.2.3)

[vzihome]

Originally Posted by arrrghhh

Uhhh.... What I said doesn't have anything to do with NAND. Please don't mix what I said in another thread with this thread... HaRET & NAND are separate things, let's keep them separate!!

You might want to put that on title, i got confused too until i read the startup.txt

Sent from my Touch Pro 2 using Tapatalk

[[ACL]]

Fellas, i hope you all party tonight and celeb the new years. We did good work in 2011 and I'm looking forward to the challenges 2012 brings us..

[muziling]

Originally Posted by [ACL]

Muz, thats not how it works on nand. THe csv files must be on /etc. Also Ive already done all of this on .27 nand and people have been using it for over a week now so what makes you think .27 has no sound?

ALso in the future, yes we will go .35 but not until we have a first full rom release out.

I compile kernel with latest source on git sever (updated to Dec 30), use new kernel and new audio lib, no sound.
Audio lib will use sdcard csv file if exists, https://github.com/acl/device_htc_rh...acoustic.c#L32

Happy New Year! =D>


EDIT: file in /etc is AudioFilter.csv,AudioPara4.csv,AudioPreProcess.csv
new audio lib read AudioFilterTable.csv,AudioPara3.csv,AudioPreProces sTable.csv
this is why no sound, solved. CDMA mode still no in-call ringtone.

[milda25]

I have 2 questions, guys. I don't know, if this is issues or functionality "by design".
1) If I disable data in Settings-Wirelles&network settings-Mobile networks and leave enabled Background data and Auto-sync in Settings-Accounts&sync settings, my Rhod100 doesn't go to sleep (LED lighting orange).
2) I asked a few days ago, but with no response. So sorry for the repeated question. After install new release from 21.12.2011 with new acoustic code have volume of my Rhod strange manners. My ringtones and alarms have growing volume and volume of notifications is too low, even if I have sets the higher volume by the button on the left side of phone. Low notification volume is probably caused by the growing volume. The notification is short sound and its ended before the volume is growing to highest volume. The in-call volume of speaker is too high, even if I have sets the lowest in-call volume.

Is this two points issues and will be solving? If you need some logs, let me know, please.
Thanks.

[[ACL]]

Originally Posted by milda25

I have 2 questions, guys. I don't know, if this is issues or functionality "by design".
1) If I disable data in Settings-Wirelles&network settings-Mobile networks and leave enabled Background data and Auto-sync in Settings-Accounts&sync settings, my Rhod100 doesn't go to sleep (LED lighting orange).
2) I asked a few days ago, but with no response. So sorry for the repeated question. After install new release from 21.12.2011 with new acoustic code have volume of my Rhod strange manners. My ringtones and alarms have growing volume and volume of notifications is too low, even if I have sets the higher volume by the button on the left side of phone. Low notification volume is probably caused by the growing volume. The notification is short sound and its ended before the volume is growing to highest volume. The in-call volume of speaker is too high, even if I have sets the lowest in-call volume.

Is this two points issues and will be solving? If you need some logs, let me know, please.
Thanks.

Autosync i noticed adds a delay to the sleep process. But i eventually does go to sleep. So give it a minute or so and see if it eventually goes green.

As for the growing volume, well there are tons of variables that may play a roll here. One thing i forgot is that each rhod may have a diff csv files. I may need to collect all the variants csv files so we can package them like we package the keyboard files. Right now i just released the rhod300 or 400 (not even sure which ones i put out). Remember this was just a test and when we merge it into the build we can come up with a clean solution.

One question i have for everyone now is if they have been able to "Power Down". Ive been working on the 3.5mm so i made a few changes and one thing that is not working for me is PowerDown. So can people report back if they have been ? If it actually locks up, then thats a diff version of the smd bug which still needs to be fixed.

[milda25]

Originally Posted by [ACL]

Autosync i noticed adds a delay to the sleep process. But i eventually does go to sleep. So give it a minute or so and see if it eventually goes green.

As for the growing volume, well there are tons of variables that may play a roll here. One thing i forgot is that each rhod may have a diff csv files. I may need to collect all the variants csv files so we can package them like we package the keyboard files. Right now i just released the rhod300 or 400 (not even sure which ones i put out). Remember this was just a test and when we merge it into the build we can come up with a clean solution.

One question i have for everyone now is if they have been able to "Power Down". Ive been working on the 3.5mm so i made a few changes and one thing that is not working for me is PowerDown. So can people report back if they have been ? If it actually locks up, then thats a diff version of the smd bug which still needs to be fixed.

As for sleep - I tried again, waited twenty minutes and all this time the led was orange It's unpleasant for me - I'm disabling data due to power saving my battery using the widget on home screen, so I must go to settings anyway and disable auto-sync. But I must say this is thing without which I may live .

As the growing volume - your answer is OK for me, thanks. I only didn't sure if this is known thing. Thanks again, ACL.

As the PowerDown - I'm not sure if I understood correct. Do you think, if we may have to PowerOff (not reboot) our rhods after the pressing the Power button on the top of the device?

[anish88]

Originally Posted by [ACL]

Autosync i noticed adds a delay to the sleep process. But i eventually does go to sleep. So give it a minute or so and see if it eventually goes green.

As for the growing volume, well there are tons of variables that may play a roll here. One thing i forgot is that each rhod may have a diff csv files. I may need to collect all the variants csv files so we can package them like we package the keyboard files. Right now i just released the rhod300 or 400 (not even sure which ones i put out). Remember this was just a test and when we merge it into the build we can come up with a clean solution.

One question i have for everyone now is if they have been able to "Power Down". Ive been working on the 3.5mm so i made a few changes and one thing that is not working for me is PowerDown. So can people report back if they have been ? If it actually locks up, then thats a diff version of the smd bug which still needs to be fixed.

so did the logs i sent you ever help to getting that whole no sound on the whole phone ever get fixed?

[arrrghhh]

Originally Posted by milda25

As the growing volume - your answer is OK for me, thanks. I only didn't sure if this is known thing. Thanks again, ACL.

As the PowerDown - I'm not sure if I understood correct. Do you think, if we may have to PowerOff (not reboot) our rhods after the pressing the Power button on the top of the device?

Either the CSV's or the acoustic code in general needs to be updated...

Power down as in hold the power button and choose shut down.

Originally Posted by anish88

so did the logs i sent you ever help to getting that whole no sound on the whole phone ever get fixed?

IMHO ACL just needs to make sure he's using the newest acoustic stuff, emwe did a lot of tweaking and fine tuning. Haven't had audio die on HaRET acoustic in a while in other words .

[mbellot]

Originally Posted by [ACL]

One question i have for everyone now is if they have been able to "Power Down". Ive been working on the 3.5mm so i made a few changes and one thing that is not working for me is PowerDown. So can people report back if they have been ? If it actually locks up, then thats a diff version of the smd bug which still needs to be fixed.

Just checked and my Rhod400 powers down just fine (and went into charge mode since it's connected right now). The only thing I'm not running fully up to date is LK. I asked if it was possible to update without wiping the phone but never got an answer so I left it alone for now.


I've noticed in-call (earpiece) volume is quite high with the latest kernel.

Are the csv files untouched from WinMo? If so, I can try swapping out the ones I was using with Froyo to see if they make a difference.

Otherwise things have been very stable since the last kernel update.

[[ACL]]

Originally Posted by mbellot

Just checked and my Rhod400 powers down just fine (and went into charge mode since it's connected right now). The only thing I'm not running fully up to date is LK. I asked if it was possible to update without wiping the phone but never got an answer so I left it alone for now.


I've noticed in-call (earpiece) volume is quite high with the latest kernel.

Are the csv files untouched from WinMo? If so, I can try swapping out the ones I was using with Froyo to see if they make a difference.

Otherwise things have been very stable since the last kernel update.

ahh ok, well it may be just my changes that messed up the power down then.

The files are unchanged but im not exactly sure if they are from the 300 i have or the 400. Thing is this whole acoustic change was made to fix the gsm rhod mic not working issue. But i'm not exactly sure which ones i packaged up. We need to see if all the rhods carry diff files or not.

also updating LK will wipe almost everything. Since "almost" is not good enough when doing updates. I recommend doing a regular backup and restore when updating LK. The only real change was the ability to reboot into android without getting stuck on fastboot. So you can always wait for the next full release since this is just a test we have now.

Thanks for the feedback.