Develop Bugs

Desire build for Kaiser (SENSE)

Here is a desire build I have been tinkering around with for a long while. There are several several issues still in need of work so I am going to leave it to the community to help me out.
I failed to mention this is a full NAND install
I will get some screen shots up as soon as I can get time.
Much faster and much more responsive in my opinion than the legend / hero / mytouch builds
Here it is in a nutshell
- I am not a hardcore developer I have just been using existing files and putting something together that works most optimal. This build has a lot of polymod, and mssmison mixed.
- Hardware keyboard does not work correctly while using Rosie, disable Touch Input to correct this issue. Also speeds up system somewhat.
- clock.sh is in /system/bin use at your own risk It is only there for those that wish to use it is not enabled at boot. Modify sysinit.rc for this
- Disable vibrate on ring and quiet when phone is moved helps with incoming calls
- This build will leave approximately 37mb of free space for data, I do store apps on SD but it is a little unorthodox maybe someone can do better than me. I create an app folder on sdcard and symlink to it. I do not recommend this but I will be upgrading soon and could careless about damaging my cards they are old.
- Livewallpapers are questionable I don't use them or like them If they dont work and you want them then you are welcome to work on their developement.
- Bluetooth not working Help Please
- Wifi not working Help Please
- Widgets may need influenced to work just go to applications / manage applications / Find HTC Sense and Force stop and Clear Data if widgets do not load on boot.
- First boot takes an extreme amount of time.
- CompCache is disabled use it if you will I find that it causes stability issues try to keep the mem size down to 28 or less if you use it.
- Media folder is not built into this system it is included in the download just add it to your sdcard should look like this /sdcard/media
ONCE AGAIN I AM NOT A DEVELOPER I WILL WORK ON WHAT IS OUTSTANDING AS I GET TIME. I MAY OR MAY NOT MAINTAIN THIS BUILD IF YOU HAVE A FIX FOR ISSUES PLEASE PM ME I WILL UPDATE FIRST POST TO REFLECT THE FIX AND BY WHO.
DOWNLOAD
USE ONE OF THE 320x480 NBH FILES FOR YOUR KAISER

Why you name it Desire build.. android on desire looks differently

Michga said:
Why you name it Desire build.. android on desire looks differently
Click to expand...
Click to collapse
This is an old build, mssmison put it out as a sdcard install on the vogue a long time ago before the legend builds were put out. I kept hold of it and tweaked it to work on my kaisers nand. That is why it looks much different than the most recent builds

Post it in the vogue forum. They get more attention so easier chance of a wifi/bluetooth update.

kallt_kaffe can probably help you with the wifi.

Dukenukemx said:
kallt_kaffe can probably help you with the wifi.
Click to expand...
Click to collapse
Try this (NOT TESTED!). I actually think just putting the correct wlan.ko in /system/lib/modules might be all it takes but I included the usual stuff just in case.

does anyone have a mirror for this build. I would like to try it out

Does anyone have market problem. I can't even enter the market, it just kick me out

crackeyes said:
does anyone have a mirror for this build. I would like to try it out
Click to expand...
Click to collapse
It should download for you I just checked it to make sure it was still validwhat issue are you having

BLAZN 2.2.2 Eta: PROJECT SOON TO BE DISCONTINUED

First off, there is an insanely huge list of guys who are responsible for making this possible.
Thanks to phhusson, dbz, Stinebd, ACL, arrrghhh , viruscrazy, WisTilt2, Klinux, kama, Reefermattness, chkms, davidebeatrice, elroy944, kstephens98, DracoLX, zenulator, Chamonix, Makkonen, Mrpippy, cr2, Markinus, Babijoee, Lmiller1708, natemcutty, and anyone else forgotten!. I WILL ADD MORE
SPECIAL THANKS TO THE NAND TEAM. ACL AND THE A TEAM
THANKS TO F22 FOR HIS KERNELS
THANKS TO VIRUSCRAZY FOR HIS CAMERA KERNELS
BLAZN 2.2.2 2011.03.06
CHANGE LOGS
youtube in HQ. man this looks like DVD. MAKE SURE WHEN OPEN YOUTUBE FOR THE FIRST TIME. CLICK MENU, SETTING, ENABLE HQ ON DATA. THEN GO ANY VIDEO TO TEST IT.
camera. works great with a new camera app.
camcorder. works super nice. no sound. i hear people saying it's working. i thinks rhod user having issue with video sound. i'm doing some testing about this.
gps.
3g. super super super fast 3G.
data. super super super fast data.
google goggles. works like it charm.
wifi is fixed
theme is fixed
and many many many more
not working
3.5 jack
BT
MMS.
APPS
all stock apps
astro
add it more app. look for it in files folder
NOT WORKING IN THIS BUILD
MMS
BT. so far not for rhod. my 2 friend, one with a blackstone and the other with diamond, they told me is working for them.
3.5 MM jack
PREPARE YOUR SD CARD
1-FORMAT YOUR SD CARD TO FAT32. FULL FORMAT
2-DOWNLOAD FROYO 2.2.2 BLAZN
3-UNZIP IT INTO YOUR SD CARD. ANDBOOT OR TO ROOT SD CARD
4-USE YOUR STARTUP.TXT FOR YOUR DEVICES. ADD THIS COMMAND YOUR STARTUP. rel_path=andboot.
5- for cdma devices. add this command for the camera on your startup. board-htcrhodium.is_cdma=1.
for gsm devices. add this command for the camera on your startup. board-htcrhodium.is_gsm=0.
FOR CDMA PHONES. REMOVE THE SIM CARD
6- for cdma & gsm devices make sure you have this command on your startup for data. force_cdma=1. for gsm devices is force_cdma=0
SETTUP FROYO 2.2.1 BLAZN FOR THE FIRST TIME
1. On WinMo, navigate to the andboot or root sd card folder on your SD card and launch haret.exe.
2. First boot will take several minutes for the data.img to be created... Be patient... enjoy the animation.
3. Do not touch. Wait for green light, you are at the home screen. Wait for green light.
4. Open Spare Parts and change End button behavior to go to home
5. Go to to Settings - Call setting and set up your voice mail for sprint,verizon. etc..
6. Go to Settings - Sound. Test the volume settings, test phone ringtones and notification ringtones
7. Go to Settings - Display-Brightness. automatic brightness. screen timeout set it to 10 minutes
8. Go to Settings - Location & security- Enable use wireless networks and gps
9. Go to Settings - Applications- Enable unknown sources
10. Go to Settings - Language & keyboard - Set your language or use more locale 2 to add language. Press the menu key and follow the screen.
11. Go to Accessibility. this is the power button ends call. check it
12. Now you can sync your phone by going to Settings - Setting account & sync
13. Let the phone sync. Do not touch. Wait for green light
14. Open all apps to get full performance. Make sure all apps fully open.
* DO NOT OPEN CAMERA.APK UNTIL YOU HAVE SWITCHED TO THE CAMERA KERNEL ON FUTURE BOOTS
* Open the market app LAST - allow it to do updates for existing apps
15. Boot back to WinMo
16. Open File Explorer; you can now switch to the camera, 1250 or 1253 kernel located in the files folder; just copy the zImage and modules*.tar.gz to the andboot folder level.
* files\first boot zimage and modules 1276 - kb backlight
17. Boot haret, alway wait for green light. Make a test call, send a text, tell someone to call you. Tell someone to send you a text.
Requirements:
* Your WinMo needs to be running at stock speed (528Mhz); DO NOT OVERCLOCK under WinMo before booting to Android, it will just crash. Don't ask how, it just doesn't work. You need to be running WinMo at stock speed since your last boot; you can't just throttle it down to stock speed and then launch Android.
* Optional but recommended: backup the data on your SD card, format it using SD Formatter as FAT32, restore your data on it, and create the Froyo X distribution with the instructions below.

Reserved
==============

THINGS YOU NEED
Current Kernel Builds
http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Current rootfs Builds
http://files.xdandroid.com/rootfs/
Current initrd.gz Builds
http://files.xdandroid.com/initramfs/
Frequently Asked Questions
http://sites.google.com/site/androidport/faq

still non-partition version, can release partition version(has npkinstall folder)

Well.. This is a useless thread and a major letdown..

great work tiad
you are awesome tiad8 great work you are soooooo active
thanks tiad and we want more and more biulds

muziling said:
still non-partition version, can release partition version(has npkinstall folder)
Click to expand...
Click to collapse
Sounds like you are looking for Neopeek. You should try there.
Thelightning87 said:
Well.. This is a useless thread and a major letdown..
Click to expand...
Click to collapse
People must eat!
Must consume!

starter to test BLAZN 2.2.1
man, browser, 3g and market downloads are super super fast. i mean fast.
it's coming
thanks

oh man can't wait for this.....go...go....go.....

hi, guys. UPDATE ON BT
my best friend leave 25 miles from me. he got a blackstone phone. he just call me. he said he can use BT on his car.
i add it info on the build.prop about BT, i add it permission for BT on system/etc and on my startup.txt i add it this line hw_bt.enable=1. i told him to enable BT on WM first.
don't know if this works, i don't have BT on my card.
his going to call me later to confirm what he did.
thanks

sounds good !
I have a blackstone and can't wait to test this version!
Thanks a lot for your amazing work on android for our htc phones!

Update BLAZN
Well guys. I been testing the new blazn. I just got to tell you guys, I'm really impress with this build. This build it so good and fast, I'm listening to pandora while I'm writing this words.
You guys will get. A mix of 3 diffrerent build. FRX03, FROYO X, AND BLAZN. I use the speed of froyo x, to get fast data, like 3g, market, market download, and a fast browser. I use the stability of frx03 to get a very stable build, and I use the blazn theme to give this build the final look. Look amazing
Thanks

tiad8 said:
Update BLAZN
Well guys. I been testing the new blazn. I just got to tell you guys, I'm really impress with this build. This build it so good and fast, I'm listening to pandora while I'm writing this words.
You guys will get. A mix of 3 diffrerent build. FRX03, FROYO X, AND BLAZN. I use the speed of froyo x, to get fast data, like 3g, market, market download, and a fast browser. I use the stability of frx03 to get a very stable build, and I use the blazn theme to give this build the final look. Look amazing
Thanks
Click to expand...
Click to collapse
Do you think you can me a favor and let me know what in FROYO X makes data faster? I had some complaints that all the XDAndroid builds are much more stable, but much slower on 3g. Wifi they said is about the same, but I've had complaints that 3g is significantly slower. If there is something we can do to improve that on the XDAndroid builds, I'd love to apply it. Thanks!

It warms the heart to see Arrrrghhh and Tiad8 working together!
It can't get much sweeter than this!

arrrghhh said:
Do you think you can me a favor and let me know what in FROYO X makes data faster? I had some complaints that all the XDAndroid builds are much more stable, but much slower on 3g. Wifi they said is about the same, but I've had complaints that 3g is significantly slower. If there is something we can do to improve that on the XDAndroid builds, I'd love to apply it. Thanks!
Click to expand...
Click to collapse
Ok. Everything start with the build.prop, I add it a few commands. I add 5 drivers to the system/lib/modules. And few other things. When I get home I will pm you all this info.
Thanks
FROYO X/SPRINT TOUCH PRO 2/RHOD

tiad8 said:
Ok. Everything start with the build.prop, I add it a few commands. I add 5 drivers to the system/lib/modules. And few other things. When I get home I will pm you all this info.
Thanks
FROYO X/SPRINT TOUCH PRO 2/RHOD
Click to expand...
Click to collapse
Thanks man. I haven't independently confirmed, but if it's true I want to spread the fast data to the vanilla bundles. You are doin great work making custom builds - keep it up.

scattaman said:
It warms the heart to see Arrrrghhh and Tiad8 working together!
It can't get much sweeter than this!
Click to expand...
Click to collapse
**** doesn't stink until you poke it......

It warms the heart to see Arrrrghhh and Tiad8 working together!
It can't get much sweeter than this!
Click to expand...
Click to collapse
**** doesn't stink until you poke it......
Click to expand...
Click to collapse
Your right, good thing this isn't ****
-------------------------------------
Sent via the XDA Tapatalk App

Data Image
Tiad AAAAarrgghhhhhh
will we be able to use our current Data Image from FRx03 with this or will we have to start over?

BigOnes69 said:
Tiad AAAAarrgghhhhhh
will we be able to use our current Data Image from FRx03 with this or will we have to start over?
Click to expand...
Click to collapse
You can try, but no promises. Usually when you go between system images you need a new data.img.
If you have weird odd issues, delete your data.img. That's troubleshooting step #1 if you have issues that nobody else does.
Titanium Backup makes it much easier.

[TESTING] XDAndroid GBX0C 2.3.7 Build

Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!​
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install​
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download

Caveat List​​
CDMA users might get a crash in phone.apk and no service on boot. If waiting doesn't resolve the issue, then reboot. Should come up fine...
BT might still be flaky
The CSV files from a RAPH100 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
GBX0C Changelog​​
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...

Test device: RAPH100 running latest NRG build w/sencity
Using everything supplied in the previous posts above minus my ts-calib file; everything seems to work on my RAPH100 (I'm not sure it matters that it has the orange brand on the back cover). Also, this does include sound! I booted without a SIM (yes, this is a GSM version RAPH). The first time I booted, it rebooted to winmo; second time was the charm.
Additional info(statistical maybe?):
Time to boot animation: 3 minutes
Time from boot animation to home: N/A (after 3 minutes my device rebooted to winmo on first try)
(Second trial)
Time to boot animation: 1 - 1.5 minutes (maybe 2 minutes?)
Time from boot animation to home: S/A (same as above)
*Successful boot to lock screen after second boot* (I wonder should this be expected behavior?)
NOTES: Hard keys "Home" and "left arrow"/back key remain highlighted after activated but deactivate after playing around(for the lack of a better word) and/or screen times out. (My opinion)At the very least it doesn't go crazy like earlier froyo builds. Also note that wifi should be working (works on mine) with this build and kernel package (included with package). (I like)New power off boot menu (long press of power key brings this up while short press seems to turn off screen, as usual). "Silent mode" (as expected), "Airplane mode" (as expected), "Kexec" (not sure yet, seems to be the same as "Reboot" or probably vise versa?), "Reboot" brings you all the way back before boot animation and "Power Off" (as expected).
Still test driving (more to come!)

R^7Z said:
"Kexec" (not sure yet, seems to be the same as "Reboot" or probably vise versa?), "Reboot" brings you all the way back before boot animation and "Power Off" (as expected).
Click to expand...
Click to collapse
So reboot didn't work properly?
Let's focus on what's changed. Audio mainly... I do appreciate the report tho .
Kexec is for swapping kernels. This way you can swap kernels and not have to go back to WinMo... Goooogle it .

I ran it for a day, and had no audio problems
only had a few small problems:
it did reboot once
orientation is inverted but i never use auto rotate
market is kinda slow
Edit:
had another reboot during gps app, and i think previous reboot might also have been while gps app was opend
but audio seems to be perfect atm
Greetings
Jeroen
DIAM100

So I've been in the Windows Mobile for quite sometime, came back and noticed the new Gingerbread Build, and it runs fine thus far... I have two issues, no google maps or facebook (incompatible with this device)? Is this something new, or unique to gingerbread?

Problem Solved...
An update to my previous post... changing the DPI back to 240 in startup.txt has resolved the problem.

I really want to try this, as the FRX build lacked the ability to use Bluetooth. Only problem is, I have no .csv files in my WinMo directory. I am running the Energy Sense ROM 2.5 29017.
What do I do now? Do I really need those files?
EDIT: Never mind. I'm an idiot! But I do only have 5 .csv files.

I have it running now, but I get no audio from the phone. Also, bluetooth pairs but I get no audio from it either.
I have a RAPH800, BTW.

SkinsFan said:
I really want to try this, as the FRX build lacked the ability to use Bluetooth. Only problem is, I have no .csv files in my WinMo directory. I am running the Energy Sense ROM 2.5 29017.
What do I do now? Do I really need those files?
EDIT: Never mind. I'm an idiot! But I do only have 5 .csv files.
Click to expand...
Click to collapse
I've also only 5 .csv files in my windows folder:
AudioFilterTable.csv
AudioPara.csv
AudioPara3.csv
AudioPreProcessTable.csv
TIAGC.csv
In the second posting from arrrghhh you will find the *.csv for the RAPH100 in a zip archive (http://forum.xda-developers.com/showpost.php?p=20869601&postcount=2 - it contains only 4 .csv files).
I've tested this Release on my RAPH100 and it is running well.
- Phone works
- Audio works
- Wireless works
- Camera works
On my phone, the hardware buttons light up irregularly (without touching or pressing them - see attachement). The result is that the focus on the screen jumps back and forth. This happens at irregular intervals. Has anyone else this problem?

(I think) It's a design flaw by HTC. This has been a long standing bug even without Android (it's just not as apparent in winmo) and unless we can figure out how to either ignore the additional key pressing being picked up by the touchpad sensor or possibly ignore the touchpad altogether, we may just have to "deal" with it as is. However, I think this is starting to get away from the actual intent of the XDAndroid team's intent to find out about noting any audio irregularities with these files. I'm guessing we either need to start posting our csv files or figuring out what the differences in changing the values mean in terms of audio(or perhaps both?). I really haven't had the time to do much testing aside from describing my experience with loading the GB test bundle.

R^7Z said:
(I think) It's a design flaw by HTC. This has been a long standing bug even without Android (it's just not as apparent in winmo) and unless we can figure out how to either ignore the additional key pressing being picked up by the touchpad sensor or possibly ignore the touchpad altogether, we may just have to "deal" with it as is. However, I think this is starting to get away from the actual intent of the XDAndroid team's intent to find out about noting any audio irregularities with these files. I'm guessing we either need to start posting our csv files or figuring out what the differences in changing the values mean in terms of audio(or perhaps both?). I really haven't had the time to do much testing aside from describing my experience with loading the GB test bundle.
Click to expand...
Click to collapse
Eh, we really just want to know if there are any dramatic differences in the CSV's between devices - XDAndroid tries really hard to support WAY too many devices .
So this thread is mainly to find out if all our new changes dramatically break any one device. Doesn't seem like it... so the next step is to aggregate all the CSV's together (why I asked everyone to post theirs) and see if we can make a big mix of them, or if we'll have to do it similar to the keyboard layout where each device gets its own folder... then it gets into proper variant detection, etc. Hairy!
But yes, the touch panel issue has ALWAYS been present folks. Let's not rehash old bugs, that doesn't do anyone a darn bit of good. Thanks!!

arrrghhh said:
But yes, the touch panel issue has ALWAYS been present folks. Let's not rehash old bugs, that doesn't do anyone a darn bit of good. Thanks!!
Click to expand...
Click to collapse
I haven't heard from this issue before. So it is good to know that.
I've compared your 4 csv files with mine (RAPH 100 - running with Energy ROM 29022) and there is no difference between them.
I've one additional csv file in my windows folder (TIAGC.csv). If you need it I can upload it.

I have a RAPH800 (Sprint) and I was in the process of doing the Pre-install Prep with Total Commander to get the .csv files. However after copying the files to my SD card, I see only 5 files.
AudioFilterTable
AudioFilterTable_Raphael#C
AudioPara3
AudioPara3_Raphael#C
AudioPreProcessTable
I don't see the AudioPara file. Am I doing something wrong? What should I do?
Also I did a Beyond Compare comparison between the files from my phone and the downloaded RAPH100 files and the files are not the same.

ericdabbs said:
I have a RAPH800 (Sprint) and I was in the process of doing the Pre-install Prep with Total Commander to get the .csv files. However after copying the files to my SD card, I see only 5 files.
AudioFilterTable
AudioFilterTable_Raphael#C
AudioPara3
AudioPara3_Raphael#C
AudioPreProcessTable
I don't see the AudioPara file. Am I doing something wrong? What should I do?
Also I did a Beyond Compare comparison between the files from my phone and the downloaded RAPH100 files and the files are not the same.
Click to expand...
Click to collapse
Every phone model will probably have different files. You didn't do anything wrong. Just use the files for your device.

Hi guys,
do you see any kind of battery consumption improvement over FRX release?

shinden said:
Hi guys,
do you see any kind of battery consumption improvement over FRX release?
Click to expand...
Click to collapse
Not really no. Weren't really expecting one either, the only thing that changed was userland. Same kernel (for the most part).

Been running GBX0B 2.3.7 Build on Fuze since the 31st.
I didnt have 10 .csvs, so i just used the his zip. Took me 3 times to get a stable build, they kept self destructing.
Sound: Perfect
Gps: Faster than FRX07.1, when it worked. I justed stop using it
Data: Only used Wifi, works fine
I have a sim in the Fuze, but i have no service.
FRX07.1 would drain my battery over night even plugged in to the wall. GBX0B 2.3.7 fixed that.
I get alot longer battery life. I got maybe 5 (est) hours with FRX07.1, 8 - 10 (est) hours GBX0B 2.3.7
This is the BEST android build for fuze (and i have tried them all).
Smoother, little faster. GPS works alot better. I think we finally got a build we can run full time

popetorak said:
Been running GBX0B 2.3.7 Build on Fuze since the 31st.
I didnt have 10 .csvs, so i just used the his zip. Took me 3 times to get a stable build, they kept self destructing.
Sound: Perfect
Gps: Faster than FRX07.1, when it worked. I justed stop using it
Data: Only used Wifi, works fine
I have a sim in the Fuze, but i have no service.
FRX07.1 would drain my battery over night even plugged in to the wall. GBX0B 2.3.7 fixed that.
I get alot longer battery life. I got maybe 5 (est) hours with FRX07.1, 8 - 10 (est) hours GBX0B 2.3.7
This is the BEST android build for fuze (and i have tried them all).
Smoother, little faster. GPS works alot better. I think we finally got a build we can run full time
Click to expand...
Click to collapse
hmmmmmmm, on my RAPH100 battery discharges faster than on FRX07.1

drugusv said:
hmmmmmmm, on my RAPH100 battery discharges faster than on FRX07.1
Click to expand...
Click to collapse
Honestly the battery shouldn't be different at all. The kernel didn't change much at all in the battery saving or sucking department.
As always, if you use the device a lot - and use a lot of the hardware (GPS, wifi, etc) it will suck your battery dry.

[APP] SwitchMe Root Profile Manager needs GSII testers please!

Hi everyone. Im one of the developers of SwitchMe, and app that allows multiple secure logins into separate installations of android on a single device. The pr is after the break.
I really need a few people to check into some issues people on some ROMs have been experiencing. There are some warnings involved:
- testers must perform a full nandroid backup before using the app, it is not our responsibility if you start getting boot loops
- if you report results or bugs, please use the "Write to us" function in the app whenever possible, and always describe the issue in the header of the logs you send
- if you post here, bes sure to include your device type and rom
- if you have apps installed on sd, be sure to mention that as well
--------------------------------------------------------------------
SwitchMe is a unique application for root users that allows you to log in and out of multiple installations of Android just as you would on a desktop computer.
The technology behind SwitchMe saves all of your applications and data, protects it and stores it as a file in memory. You can then log out of an
account and log into a fresh installation of Android or another account with its own unique content.
You may create as many profiles as the memory is capable of holding. Some of these may require very little free memory because they contain few apps,
others will be larger as they contain many applications and lots of cache and data.
Why is this functionality useful?
Privacy - the most obvious benefit is that you can securely share one device among multiple users, which gives you privacy and peace of mind.
Testing - if you are a developer, you can use profiles as clean sandboxes to test your applications and their interaction with the system.
Gaming – with multiple installations of Android on a single device, you can now play online MMOs as different characters.
Speed - the games your kids play slow down your tablet, but with SwitchMe you can easily create profiles without games or instant messengers.
Battery life - when the battery is low but there are important emails or documents to edit later, switch to a profile which only contains these essentials.
These of course are only suggestions - there are plenty of other uses for the functionality SwitchMe offers.
Market link:
https://market.android.com/details?id=fahrbot.apps.switchme
The Lite version allows the creation of two profiles, enough to test on.
Screens:

SwitchMe 1.2 has been rolled out and now includes a lockscreen replacement:
1.2
Added lock screen for logging in and out
More stable Fast switch implementation
Reworked UI colors
Now, its very important that we get some feedback on how this big new feature works, so please read up on it in the help and post your thoughts!

1.2.2 - HOTFIX 2
Reworked widget on qHD+ displays
Fixed widget text on HC and ICS
Fast switch improved on older devices

Nice, thanks!

Thank you! Any issues to report?

What do you think of yesterday's update?

1.4.3.7
Fixed device specific switch screen crashes and issues
Fixed UI bug in switch screen preferences
If anyohe had problems with superuser before, this should fix them. Please let me know if that is the case, its important we get some feedback here!

This is working perfectly with CyanogenMod 9. Will this continue to work if I update to a newer nightly?

xethor said:
This is working perfectly with CyanogenMod 9. Will this continue to work if I update to a newer nightly?
Click to expand...
Click to collapse
I dont see why not. Just make sure you back up your profiles to the SD card if you do a wipe.
They are in /data/.profiles. Next release will have an im-app backup function.

1.5.3.0
Enabled full support for MIPS and x86 architectures
Many root daemon code fixes and optimizations implemented
Sorry backup is relegated to the next release.

Thought I should let you guys know of the issue I had with the paid version of this earlier.
Running Hyperdroid Androidmeda 6.1.17, I rebooted my phone and SwitchMe would ask me to log in, however it wouldn't list the username, wouldn't log in when I put the info in myself, and wouldn't even say the password was wrong when I entered it wrong on purpose. I tried multiple reboots etc, the issue persisted.
Unfortunately I don't have a logcat or anything since I was in a rush to get my phone working properly (had to leave soon) so I restored a nandroid from before I installed SwitchMe
This was all before the 1.5.3.0 release btw, happened last week.

Yes, that was hotfixed a few hours later. The main thread also has a flashable zip which will "unswitchme"

THANKS good
ftgg99 said:
Yes, that was hotfixed a few hours later. The main thread also has a flashable zip which will "unswitchme"
Click to expand...
Click to collapse
thanks goo work

Enjoy! And spread the word

This thing is rock solid thanks very much

Thanks, by the way we released a new app today some of you might also find useful, you can find it here:
http://forum.xda-developers.com/showthread.php?t=1538222
PLEASE CHECK IT OUT AND BE KIND
Touch Blocker Beta - a simple but useful app that makes holding and using your device easier
There are two basic functions:
- create dead zones where touches do not register
- filter the screen when reading in low light
We are already in a relatively stable Beta release - whats left now is adding new features and making it all look pretty. You can follow this process at the thread here.
Please be sure to write suggestions - we are looking forward to engaging the community and building a useful and nifty application that many will enjoy!
Market link
https://play.google.com/store/apps/details?id=fahrbot.apps.touchblocker
Screens
Debugging
If you experience issues, the best way to help is by reproducing them and then clicking "write to us" - be sure to include a description of your error or we may not read the logs.

1.5.3.1
Fixed issue with lock on boot
Fixed some rare crashes on lock screen
Fixed MIPS and X86 Key compatibility

Any issues with the latest version?

I take it everything is fine?

Any issues to report?

[ROM][5.0.2/LRX22G][AOSP][LINARO/OPTIMIZED] FML: Fork My Life (2015/01/08)

[#Intro]
Oh, and now there's these Lollipops I'm handing out. They are free as always, and they are very very delicious.
[#Why]
[#Info]
I need people testing and finding bugs if anything is going to be fixed. I might not have the Bluetooth devices you have, I might not use the camera as much as you, I might not use 4G LTE (or mobile data in general really) as much as you; you get the idea.
[#HowTo]
Latest Build​KitKat/Stable: N/A
KitKat/Beta: omni-4.4.4-20141015-toroplus-FML.zip (162.13 MB)
Lollipop/Beta: FML-AOSP-5.0-20150108-toroplus.zip (195.53 MB)
LOLLIPOP INFO:
USE THESE GAPPS: FML-GApps-5.0.x-20150101-tuna.zip (167.81 MB)
They are based on PA's GApps, huge thank you to them!
Known Issues
- Camera can be a little touchy, but it generally works.
Lollipop Changelogs can be found in the post below!
(KitKat) BETA INFO:
Beta builds are using updated GPU drivers (and an updated kernel to go with them) courtesy of @Ziyan, as well as being up to date with the latest stuff from OmniROM. NOTE: YOU CANNOT FLASH A DIFFERENT KERNEL WITH THESE BUILDS.
Currently broken with the new GPU drivers:
- Hardware Video Decoding FIXED 2014/10/06
- Hardware Video Encoding(?) FIXED 2014/10/08
- Camera (PARTIALLY) FIXED 2014/10/08
- The stock camera app (as well as Google Camera) has this weird quirk of crashing when pressing the shutter button to take a picture, however many different camera apps on the Play Store (in particular Camera ZOOM FX) work flawlessly. Video recording is generally OK, however I've been getting some reports of the audio and video being a little out of sync, so your mileage may vary...
See the Changelog post below for..... well..... changelogs.
[#GApps]
Known Issues​- The screenrecord command does not work directly, however it does work via the Power menu.
- There can be a slight (noticeable, but not huge) delay when pressing the Recents or Home button.
[#Thanks]
[#Donations]
XDA:DevDB Information
FML: Fork My Life, ROM for the Samsung Galaxy Nexus
Contributors
MWisBest
Source Code: https://github.com/MWisBest/
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2015-01-08
Created 2014-10-13
Last Updated 2015-01-08

Changelog, News, Etc.​
Lollipop Beta Changelogs:
- Updated the camera HAL.
This is going to be a little... fragile, at first, but in the long run it's needed. Stock camera app saves pictures now at least.
You may also notice that there's a 5.1MP resolution now (clear your camera app's data if you don't see it), despite our camera supposedly being 5.0MP all these years. Turns out the sensor's native resolution is indeed a whopping 16 pixels taller and 16 pixels wider than we've been using.
2015/01/04
- Added back some of the classic FML optimizations and more.
Built with -fstrict-aliasing flag, C++11, and the Linaro GCC 4.9 toolchain.
- Updated to AOSP "android-5.0.2_r1" tag.
As usual, the only real change was them bumping the version number.
- Improved flashing.
The speed of flashing the ROM zip is now much faster.
- Superuser is now built-in.
There's no need to flash SuperSU. You can find Superuser in the Settings app. You may have to enable the "Development Settings" menu to see it.
Some apps are a little sketchy with this Superuser though, most notably Titanium Backup. If you have issues, try flashing SuperSU.
- Video playback should be fixed.
YouTube in particular seems OK. If you have some weird format you're playing back locally I cannot make any guarantees though.
- The camera situation has improved and also regressed.
The stock camera is kinda back to the point of where it was with the KitKat Beta builds:
---- Preview works. Saving photos does not work. Video recording kinda works.
--- However:
---- The camera calibration is a little messed up. Long story, but it'll be fixed soon. So your white balance may look kinda funky, among other things.
- Audio quality is improved, with support for 192kHz FLAC as well.
This is possible thanks to a new audio resampler, which doesn't impose the same sample rate restrictions of the stock Android ones. It also has far better quality than the stock Android resamplers.
- WiiMotes can now be paired via Bluetooth.
I used to be a bit of a Wii hacking enthusiast... I think I still need to add some more stuff to make it useable as a gamepad or something, but yeah.
- Fixed location services issues.
- (toro) Fixed switching between 4G/LTE and 3G/CDMA network settings.
- Kernel changes:
Reclaimed 38MB of RAM from the carveout stuff.
Removed HDMI's framebuffer, saving an additional ~16MB of RAM. With Lollipop, MHL/HDMI out isn't working with our old HWComposer, so might as well save some RAM in the mean time.
Added overclocking support, as well as adjusted the stock frequencies a little.
Added the GPU kernel driver back into the kernel, rather than building it as a separate module.
Switched to LZO compression for the kernel. It results in a slightly larger size to the kernel, but it boots faster.
Added the "purple tint fix".
Added compiler flag to tune code for Cortex-A9 CPU.
Built with Linaro GCC 4.9 toolchain.
Older Builds:
2014/11/16
- Fixed the RIL.
(I think, still unsure of toroplus's status.)
There were a few things that went into this, and I can't really take much credit for it other than being persistent in trying to fix it.
1. rild needed a little fix-up to somewhat return it to pre-Lollipop form. Basically Google is forcing Qualcomm's junk upon the world. @dhiru1602 pointed me in the direction of some commits from rmcc to hardware/ril that fixed this part of the problem.
2. The kernel needed a commit to support some new junk related to networking in Lollipop. @Ziyan linked me to the change in question.
- Updated to AOSP "android-5.0.0_r6" tag.
Really the only change is that the build number is bumped to LRX21T.
- Switched out a couple small proprietary binaries with a reverse-engineered open-source version.
Thanks to @stargo who has really been killin' it for the Motorola OMAP devices recently, we now have a reverse-engineered pvrsrvinit binary (the executable that fires up the GPU drivers on boot-up). This is especially important because the proprietary pvrsrvinit wasn't compiled as PIE (position-independent executable). With Lollipop, they're forcing everything to be PIE, which is good because PIE is better from a security stand-point. Previously I had been adding a workaround to enable support for non-PIE, which I now don't need.
2014/11/11
- Switched back to the old OTA package format.
With Lollipop they're now, by default, flashing something similar to a system.img. I switched back to the old format. THIS IS CAUSING VERY LENGTHY FLASH TIMES NOW HOWEVER, I HOPE TO FIX THESE SOON.
- Changed the kernel to build with GCC 4.7.
With Lollipop, Google switched to GCC 4.8. GCC 4.8 has never been kind to the Galaxy Nexus kernel, I'm surprised it was booting at all in the first place.
- Added "Ambient Display".
Apparently I need to add a "pick-up" or "significant motion" sensor for it though, so it displays something when the phone is picked up.
- Fixed chromium crashing.
This fixes Browser crashing upon open, among other things. This fix has been in chromium itself for nearly 4 months now, I don't know what the heck Google is doing to AOSP to make it so FUBAR lately...
- Fixed lag in Recents menu.
Now it's smoother than KitKat's, in my opinion.
- Added back F2FS support.
F2FS is now supported again, HOWEVER, it is NOT supported on the /system partition. It really didn't do any good for /system anyway.
- Updated various icons.
The Dialer icon in particular was bothering me. Other things that aren't visible in the launcher, e.g. SettingsProvider, have been fixed as well.
- Fixed FLAC playback, among other media decoding issues.
Just needed a sync-up in the device tree with one thing that I think Google DID do a nice job of with Lollipop actually.
- Built the ROM with "WITH_DEXPREOPT := true" defined.
This basically has all the system apps compiled before flashing, to cut down on the initial boot-up time which is ridiculously long with ART.
- Changed the "Android is upgrading..." screen to prevent burn-in.
Instead of using the white Lollipop-like look, it now should show up as the old, darker theme.
KitKat Beta Changelogs:
2014/10/15
- Cleaned up the kernel.
Ziyan went over all his work not long ago and cleaned up the commit history and whatnot. He's letting me do the task of merging in the GPU driver stuff, so I'm currently just getting the kernel to a "clean slate" of sorts for other kernel devs to fork and build off of. Basically this should hopefully be the new "stock" or "Google" kernel. As a result, there's some bells and whistles missing from this build. It does however include some new audio updates that weren't in the previous kernel, which leads me to this...
- Changed audio sampling rate to 48kHz.
Previously the sampling rate has been 44.1kHz. The Galaxy Nexus supports 48kHz though! Here's what mainly sparked this change: since KitKat, the UI audio effects (e.x. touch sounds) have been switching over to 48kHz. With the Galaxy Nexus still using 44.1kHz, UI sound playback became kinda sluggish, and this was a big contributor to it. The UI sounds use the "fast track" audio path (where it tries to do as little processing as it can to the audio in order to play it with a minimum amount of latency), however a requirement of using this is that no resampling (e.g. converting 48kHz to 44.1kHz, like it has been doing currently with KitKat) can be required on the audio being played. Therefore the UI sounds were taking the "deep buffer" audio path, which has a delay to it. In switching to 48kHz, the "fast track" path is actually even faster now than it has ever been previously, and the Galaxy Nexus was already TOP OF THE LINE when it comes to audio latency believe it or not!
Another thing about this is that there is now support for playback of 96kHz audio files.
- Some updates to the camera HAL.
This hasn't fixed the situation of stock and stock-based camera apps crashing when taking a picture, but it's a start on it though.
NOTICE: Poweramp (and probably most other media players that use their own native code for audio playback rather than straight-up using the built-in Android APIs) is being pissy about the sampling rate change. If you experience issues with music playing, especially things like popping or crackling, please try Play Music or Apollo and see if your issue is still present. I know the UIs for Play Music and Apollo are pretty awful, but I can't write my own media player because I'm dealing with this camera stuff!
KitKat Stable Changelogs:
N/A

Reserved
Reserved.

Reserved
Reserved.

Finally got FML up for you toroplus guys! Sorry for the long delay.

Awesome...thank you very much MW!!!!!

Wonderful
Currently uploading this to my server and will seed until a stable version is uploaded, then I will replace it. Thank you so much for bringing life into an otherwise fading device. :crying:
Donation sent.

Downloading. Will be my second rom I try;

Beeing the beginner that I am, I have a Maguro so i couldn't install this one.
Sorry.

BennyDS said:
Beeing the beginner that I am, I have a Maguro so i couldn't install this one.
Sorry.
Click to expand...
Click to collapse
Maguro Build is Here.

I've always wondered about this rom as I saw it on the toro thread... will give it a whirl

MWisBest said:
Finally got FML up for you toroplus guys! Sorry for the long delay.
Click to expand...
Click to collapse
Running good so far! I dirty-flashed over the official Omni build I've been running. No problems to report outside of the expected camera weirdness. Play Store camera apps are all over the map in their behavior - CameraZoomFX works perfectly as you reported, Google Camera crashes like the stock camera, Focal doesn't have any display at all. Video recording works but the audio is a bit out of sync, playback is a little choppy on the phone but is smoother on my computer. VideoCam Illusion (which does its own video encoding via software) does not work at all. Video hangouts seem to work fine.
Also, I used the torch quite a bit today, and at one point it quit working and I had to reboot to get it back. It's a bit early to tell, but I'm suspicious that this ROM is affected by the same 'Camera quits working' bug as Ziyan's 'stable' OMAP kernel.
Anyway, thanks again for your amazing work!

I had the same Torch issue as stated above, fixed with a reboot. Im currently running on Ting/ a Sprint MVNO and they are known for having APN issues with 4.4.x roms. When switching to LTE in the settings, the dialer app would crash loop until I switched back to 3g/2g. Flashing an APN zip on their forum fixed the crashing, but havent been able to tell if 4g actually connects as its pretty shotty coverage in my area. But I thought Id share incase someone else is on Ting.
---------- Post added at 05:15 PM ---------- Previous post was at 05:04 PM ----------
Coming from CM 11 I guess I have been lucky as far as not having to do my own work as far as updating the Sprint Profile, and PRL as it was still within the system settings. I have been unable to figure out how to update Profile/PRL on my own as of yet. Any chance one of you may want to share this info? I'd greatly appreciate it.

New build is up.

The ROM is running smoothly with a few hiccups. I have ran into a few problems. Here's some of them that I have found so far:
1. I currently don't have root.
2. The options to "Uninstall/App info" is there but the texts aren't visible.
3. 3G to LTE switching isn't working on the 20141015 nightly build. It was on the 20141014 nightly build.
4. No Up/Down icon on the signal.

bloopblah said:
The ROM is running smoothly with a few hiccups. I have ran into a few problems. Here's some of them that I have found so far:
1. I currently don't have root.
2. The options to "Uninstall/App info" is there but the texts aren't visible.
3. 3G to LTE switching isn't working on the 20141015 nightly build. It was on the 20141014 nightly build.
4. No Up/Down icon on the signal.
Click to expand...
Click to collapse
1. Root works here on FML. THe official build of OmniROM does not include superuser, you need to flash it yourself from recovery.
2. That's been a longstanding bug with Omni on toroplus for some reason.
3. There's no 20141014 build of FML for toroplus - are you using the Omni official build?
4. That's turned off by default - Settings/Bars/Activity Indicators.

Alright, another new build to try out! I will have a couple of ROMs to try on my GNex which is a good thing!
@MWisBest...hopefully you get some donations coming in as well as Musical_Chairs since you guys are putting time and effort into providing new goodies for us.
Hopefully you get some $$$ coming in. It's going to be about a week for me to donate. One thing people don't realize is that donations don't exactly flood in for devs. I released 4 Venum Ice ET4G ROMs and 2 fully inverted black and white Note 2 ROMs including icons, all inverted apps etc. I actually got over 1000 downloads on all 6 ROMs within the first 24 hours and had excellent feedback.... I received a total of 3 donations totaling $12! Lol. What you guys are doing is harder so hopefully some people who are still here show you guys some love for not making this a thread that got closed for inactivity.... Thanks again to both of you.
Sent from my Knox-Blocked P.O.S Tab 3 running same hardware as my GNex using Xparent Gray Tapatalk 2

Wanted to give this rom a shot mainly due to the updated GPU drivers. So far a very smooth experience and pleased with it except for one major bug for my use case: Any video playback either Youtube, MX Player, etc.. after some uptime seems to fail entirely. In the case of YT it'll just sit at a black buffering screen. It'll buffer the data fine going by the progress bar as I've at times had about 1/4 of a 10-15 minute video buffer going by that indication with no playback. If I reboot the phone and give it another shot, it works.

cr08 said:
Wanted to give this rom a shot mainly due to the updated GPU drivers. So far a very smooth experience and pleased with it except for one major bug for my use case: Any video playback either Youtube, MX Player, etc.. after some uptime seems to fail entirely. In the case of YT it'll just sit at a black buffering screen. It'll buffer the data fine going by the progress bar as I've at times had about 1/4 of a 10-15 minute video buffer going by that indication with no playback. If I reboot the phone and give it another shot, it works.
Click to expand...
Click to collapse
That's the same issue as the torch issue mentioned above. It's a hard bug to track down because it takes so long to show up, and AFAIK nobody has found a reliable way to trigger it (other than just wait a day or two for it to show up). If somebody can figure out how to trigger it more quickly, I would like to try a git bisect on Ziyan's stable OMAP kernel (which is affected by the same bug) and see if I can pinpoint what is actually causing it. But without a reliable way to tell if a particular test kernel is good or not, a bisect is more or less useless.

Hi guys. How are you? I'm fantastic right now:
EDIT: Let me fix that a little...