Database Users

Bugs in stock phone

I am assuming once you root the phone and push a custom ROM onto the phone, this will fix HTC's introduced bugs?
Bluetooth
SMS battery drain
Reverting apps versions
Stuff like this.

No, because the custom ROM is just the Sprint ROM with a few additions and modifications.

Ouch.
ok, anyone working on compiling a 2.0 kernal?

Treefallingquietly said:
Ouch.
ok, anyone working on compiling a 2.0 kernal?
Click to expand...
Click to collapse
HTC
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Although the bugs are not fixed, rooting allow one to use various workarounds that would not be possible without, and in fact for EACH of the issues you have listed:
Bluetooth: http://community.sprint.com/baw/thread/23854?tstart=0
While I cannot personally vouge for this, I have seen many posts on Sprint and here that detail the workaround described in the post as effective.
SMS Battery Drain: I think this may have actually been the first big bug discovered, and also fixed without root! Unfortunately, the default messaging app is defective, so in the meantime it is recommended to use either chompSMS or Handcent SMS from the Market until an update is released.
See this post: http://community.sprint.com/baw/thread/23043
Finally...
Reverting Apps: This is addressed on both forums, but a workaround only exists with root, and is similar in fashion to the bluetooth fix but for a different directory.
http://forum.xda-developers.com/showthread.php?t=582176
http://forum.xda-developers.com/showthread.php?t=581806
Hope this helps! I intend on posting a very detailed guide on every step of rooting, backing up, and working around most of the detailed problems in the very near future, stay tuned!

What I'd like is a kernel that will have this working as intended. But really, I am not afraid of the work arounds and the hands on work required, but if my wife had this phone with these problems, she would have chucked it out the window within days.

One more...
You left out the original bug (mentioned by briankwest, one of the first rooters), the TCP timestamp issue:
echo 0 > /proc/sys/net/ipv4/tcp_timestamps
This could also be added to the MoDaCo init.rc so it is set at each boot (otherwise it will revert back to "1").

CM7 for Samsung Admire (also known as Vitality or SCH-R720)

What the is this?
It's requisite0's build(s) of Cyanogenmod 7.2 Release Candidate 1, ClockWorkMod Recovery 5.0.2.8, and custom Kernel.
How do I use it?
1. First make sure you do a nandroid backup.
2. Flash the CWM Recovery and Kernel package, then go to Advanced->Reboot recovery. Here: http://d-h.st/tU6
3. Install the latest version of Cyanogenmod 7.2 ROM. Here: http://d-h.st/PmW
4. [The files were deleted for the step about the configuration for Cricket Wireless and nTelos]
5. Install the latest gapps (no longer necessary to mount system beforehand) zip. Here: http://d-h.st/pT4
6. (OPTIONAL) Install the overclocked kernel. Here: https://www.dropbox.com/s/2765gmtxnotqp0k/CM72RC1-OCKernel900MHz-requisite0.zip
7. Select Reboot system now and wait at least 10 minutes for the market updates to take effect (connect to wifi first if data connection isn't working)(first boot might take a minute).
What works?
Wifi
Bluetooth
Data
Texting
Cell Service
USB
Camera (video)
Data/MMS (in 90% of cases)
What doesn't work?
Camera (still pictures)
Data/MMS (in 10% of cases)
Do you provide source code?
Yes. You can check requisite0's GitHub here: https://github.com/requisite0
This is not my work, this was done by requisite0 at androidforums. I am just informing those with the Samsung Admire. Here is the original thread: http://androidforums.com/admire-all-things-root/587358-rom-cwm-kernel-cm7-2-rc1-requisite0-beta2.html

Now we just need someone to pick this rom up and complete it.For Cm7 beta2 it works well.Just a few bugs to work out.
Req did a great job with it so far.Anyone up for finishing it?

Check this forum: http://androidforums.com/admire-all-things-root/
Over at Android Forums there is support for our phone, we have devs like Boraichee, RetroDelete working on getting bugs fixed in CM7. requisite0 is banned which means if there is an update to his CM7.2 ROM/Kernel he won't be able to post it. But I noticed that your probably already know that since you are also at Android Forums.

how the hell do we do any thing if people keep uploading to mediafire!? that website is dead, its not a good website anymore.

Still waiting for the release version of cm7 Hope Req0 gets it done soon.
And thanks to Pg and others for all their work in this project.
Doug

Hi, how to fix roaming icon?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I fixed mine by deleting efi_0 from EFS using QPST

undeground88 said:
Hi, how to fix roaming icon?
Click to expand...
Click to collapse
What rom version was that? Looked newer than cm7.2

does anyone have a link to the kernel?

[Q] How do I get Chrome Beta/Stable to work?

Ok, so I'd had two ICS ROMs on my phone till date\
Quarx's CM9 Nightly for Defy+
Fuzz's CM9 euroskank kang for Defy+
I was able to install Chrome Beta and Stable on both these ROMs, but am unable to render any page in the browser. Here are some screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Connectivity to my data network is obviously not a problem since I'm being offered search suggestions and the progress bar is loading.
My build.prop already has the ICS id in it.
I've browsed the forums and people have suggested that this problem is caused by the lack of Hardware Acceleration(HWA).
So can anyone either guide me on how to go about fixing this? Or maybe a suggest a full HWA enabled ROM for me?
Thanks!

Chrome is not yet stable on any cm9 rom.

kanpurite said:
Chrome is not yet stable on any cm9 rom.
Click to expand...
Click to collapse
Thanks for replying, but stability isn't even the issue here. I've actually never been able to get a [age to render despite having no trouble installing. I've seen other people on custom ROMs using Chrome.
Anyway, is there no ROM out there supporting full HWA?

v1n337 said:
Thanks for replying, but stability isn't even the issue here. I've actually never been able to get a [age to render despite having no trouble installing. I've seen other people on custom ROMs using Chrome.
Anyway, is there no ROM out there supporting full HWA?
Click to expand...
Click to collapse
No.
Chrome doesn't work on any rom.
Regarding hwa, the closest we've got is epsylon3's rom ,where barring few apps like (play store,chrome etc) ,everything else works.
but still its a no go for chrome !

chrome will NEVER work on the defy/defy+. epsylon stated that our froyo/gb 3d driver lacks some opengl extensions chrome (and ics/hwa) would need, and with the locked bootloader we cant implement the ics driver. sorry to be the one bringin the bad news. :/
sent from my cm7 defy...

Well you can always get an iPhone, works great I might add. Haha
Sent from my MB525 using XDA

[Q] GPS-problem with mathkid's matrix kernel 9.0

Hi,
In know this doesn't belong here, but since I haven't posted yet, I'm not allowed to write in the corresponding thread.
I installed matr1x kernel 9.0 on my n4 yesterday and got massive problems with GPS. The GPS-location needs VERY long to settle if is working at all. I had the best conditions for GPS since i was walking outside in pretty open space with a clear blue sky....
Anyone got the same problems or any ideas what could be wrong, since i found nothing on this topic according to the matr1x kernels anywhere.
Okay. 9.0 is new, but someone must have noticed it if it is a general problem with the kernel.
the power-management is astonishing and I would gladly keep the kernel for that.
regards...

cythev said:
Hi,
In know this doesn't belong here, but since I haven't posted yet, I'm not allowed to write in the corresponding thread.
I installed matr1x kernel 9.0 on my n4 yesterday and got massive problems with GPS. The GPS-location needs VERY long to settle if is working at all. I had the best conditions for GPS since i was walking outside in pretty open space with a clear blue sky....
Anyone got the same problems or any ideas what could be wrong, since i found nothing on this topic according to the matr1x kernels anywhere.
Okay. 9.0 is new, but someone must have noticed it if it is a general problem with the kernel.
the power-management is astonishing and I would gladly keep the kernel for that.
regards...
Click to expand...
Click to collapse
Although I have only used the kernel for a couple of hours I've found the GPS to be spot on and very quick. Some have said changing the location in your build.prop to your correct country helps?
System>build.prop
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4

Tom540 said:
Although I have only used the kernel for a couple of hours I've found the GPS to be spot on and very quick. Some have said changing the location in your build.prop to your correct country helps?
System>build.prop
View attachment 2019879
Sent from my Nexus 4
Click to expand...
Click to collapse
thanks. I'll give it a try if the problem reoccures. For now i just reflashed the kernel and everything works fine again. maybe TouchWake was the problem since that was the only thing i changed since flashing yesterday. I will try again and see if the gps-break reoccurres.

Sony releases the binaries for Android M!

Holy smokes that was fast! Kudos Sony!
http://developer.sonymobile.com/201...-binaries-added-to-sonys-open-device-program/

Meaning the "preview" will soon perish nice
Btw, thats with 3.10 kernel?

Gonna do a build now, who's keen to flash? I doubt many things will work, mainly RIL (Phone/SMS) and Camera that I'm 99% sure wont..
Just got my phone back from Warranty so not going to unlock just yet in case it has it's own issues right away.

I think the AOSP builds have availabled for 3 months ago? Just have not been the latest binary.
Sent from my Xperia Z2 using Tapatalk

The older builds still used the old API level and didn't include all of the features from what I can see.
Build still running, could be a little while yet.
Edit: Failed - libperipheral_client.so: File format not recognized in the Sony vendor files - hmm.

XeKToReX said:
The older builds still used the old API level and didn't include all of the features from what I can see.
Build still running, could be a little while yet.
Edit: Failed - libperipheral_client.so: File format not recognized in the Sony vendor files - hmm.
Click to expand...
Click to collapse
I got the same error while building for Z1 compact. do you know how to fix it? or is this a problem with the sony binaries?

XeKToReX said:
Gonna do a build now, who's keen to flash? I doubt many things will work, mainly RIL (Phone/SMS) and Camera that I'm 99% sure wont..
Just got my phone back from Warranty so not going to unlock just yet in case it has it's own issues right away.
Click to expand...
Click to collapse
I can gladly help you by flashing it!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

coolkil said:
I got the same error while building for Z1 compact. do you know how to fix it? or is this a problem with the sony binaries?
Click to expand...
Click to collapse
Based on the image above, looks like there is some corruption in the binaries, might message jerplea later on and see if there is a fix around.

XeKToReX said:
Based on the image above, looks like there is some corruption in the binaries, might message jerplea later on and see if there is a fix around.
Click to expand...
Click to collapse
No, and no recovery for lollipop as of yet.

i've flashed the Lolipop AOSP from FXP few days ago, had a recovery included.