Develop Bugs

Rhobuntu: Ubuntu 9.04 and Debian (test) UPDATE [19/09/2010]

Important - Read First!
First of all you must know that everything you do is on your own risk. Your device was not designed to run GNU/Linux or Android and that's why you shouldn't expect everything to be perfectly safe. If you don't want any troubles then simply don't tamper with your phone. On the other hand, installing Rhobuntu is probably less dangerous than installing alternative ROM's, because it doesn't touch your ROM and runs completely from the SD card. If something goes wrong and the system would hang up, you always can remove the battery and boot into Windows Mobile. Still, we can't guarantee you anything and we won't be liable for any damage that might happen to your device. If you don't accept this, don't install Rhobuntu.
At the moment two problems are known to occur when using Rhobuntu. They are, however, not Rhobuntu specific and may also occur when using Android.
1- After booting back into WinMo, you can't install or run unsigned apps. This problem probably has something to do with the way haret kicks WinMo out of the RAM. It also seems to occur only in combination with the use of Exchange Server. The only known solution at the moment is Hard Reset. Some users also reported that it can be fixed by using Visual Studio 2008. Check out this threads:
o Not digitally signed with a Trusted certificate/ Activesync keeps UNINSTALLING!
o Program... is not digitally signed with trusted certificate. HELP!
2- Since we still have no proper battery charge indicator working, you might not notice that your battery is completely drained. Deep discharge is, however, not good for batteries and may in some cases even damage them. Here is a thread dealing with this problem when running Android
o Android killed my USB connection, please help
The majority of Rhobuntu users doesn't face these problems, but just in case, you've been warned.
WIKI http://wiki.xda-developers.com/index.php?pagename=RhodiumUbuntu
WEBSITE https://sites.google.com/site/rhobuntu/
This build by Walter79 and the Rhobuntu team:
Rhobuntu 9.04 19.09.2010
changelog:
- zimage update (Xandroid Build 16/09)
- sphone 0.04 (thanks AmiPro)
- 3G scripts update (thanks AmiPro)
- sound works partial (thanks to phhuson) !!! run /sdcard/ubuntu/playwav2 after boot !!!
- alsaplayer added
Download:
Link1: http://www.megaupload.com/?f=RWDJWUN0
Link2: http://rhobuntu.4shared.com
Debian Squeeze Test 19.09.2010
For more information please look at this post http://forum.xda-developers.com/showpost.php?p=8186181&postcount=1208
Download:
link1: http://www.4shared.com/dir/n-2ObqP_/pro2-debian.html
Old Build (27/06/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (13/05/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (14/04/2010)
*part one:http://rapidshare.com/files/375930803/Jaunty_14_04_2010.7z.001 MD5 77430e728bb17277e671cc55ae03161f and part two: http://rapidshare.com/files/375939439/Jaunty_14_04_2010.7z.002 MD5 523589000dcd5d1dcea668bbe51253af
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (11/04/2010)
* http://rs427.rapidshare.com/files/374730149/Jaunty_11_04_2010.7z
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (10/04/2010)
*http://rapidshare.com/files/374138895/Jaunty_10_04_2010.7z
*http://rhobuntu.4shared.com

Pretty cool idea, keep us posted!

Definitely an awesome idea, and one I had been thinking about myself since my original Touch Pro days. An embedded version of Linux should run great on these devices. Hopefully momentum will grow surrounding this.

thats very interesting. any pictures of this running? maybe things can be pulled from android.

THANKS!!!! downloading now!

tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.

aq3e said:
tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.
Click to expand...
Click to collapse
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?

Help!
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.

dicko99 said:
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.
Click to expand...
Click to collapse
Wierd, my winmo works find, minus the calibration issue, it's brilliant, we need some linux Devs to look into this. as a windows user, i have no idea on what to do
Thanks (All we need now is win XP )
Badwolve1

I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.

dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
did you install anything recently, could try uninstalling it

dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
try installing SdkCerts.cab
http://forum.xda-developers.com/showthread.php?t=554240
the cab is included with the rhodium keymapper zip file. (keymapper app is worth installing as well )

sdkcerts won't install. It has the same problem as other cabs where it prompts to say the program is from an unknown publisher and when I tap Yes to continue it still fails with "Installation of SdkCerts.CAB was unsuccessful."

Tried booting it up on my Verizon TP2 and all it does is run haret and then freeze.

Thanks for putting this together, sebbo90. It boots nicely, and actually performs quite well on my Tilt2. I hope some of the developers take notice of this project and consider fixing the major usability issues like the front keys and the display calibration.

After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.

spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
How did you even get it to boot?
EDIT: Do you think it will not boot for me since you all are using GSM and i am using a CDMA phone? Some settings may need to be changed i guess. I have been messing around but no luck.

spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps

sebbo90 said:
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?
Click to expand...
Click to collapse
If the mtype needs to be changed, what should it be instead of the default 2292, forgive my ignorance.
EDIT: must be a fluke, it booted now, did not change a thing. Re-extracted the ubuntu rar and shoved it back on the SD and booted. Great Job. All we need now is calibration to get started.

sebbo90 said:
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps
Click to expand...
Click to collapse
I got it working now. It was the directory structure I was using. I spent about 2 hours last night working on the calibration issue. If I could get that working it would be sweet. Tried a newer version of haret and tweaked the startup.txt a bit but the calibration still goes out of range.
On a brighter note, the calibration works fine when booting xdandroid with haret though it is a manual calibration there is hope anyway.

Bootup Error, init: untracked pid 123 exited

Ok, days of peace are finally over
Today after doing a simple reset of my kaiser (power off then back on)
I have noticed an endless loop in boot and that is the line,
set volume of 256 to 5
init: untracked pid 123 exited
Click to expand...
Click to collapse
The pid number increaments by 3 after every loop and the loop starts with
snd_set_device(1,1,1)
rpc_write(blablablabla)
blablablablabla
Click to expand...
Click to collapse
and the end of the loop is
set volume of 256 to 5
init: untracked pid 123 exited
Whats suddenly worng?
I really dont want to lose my contacts, rest of the apps/tweaks I dont care

dark_prince said:
Ok, days of peace are finally over
Today after doing a simple reset of my kaiser (power off then back on)
I have noticed an endless loop in boot and that is the line,
The pid number increaments by 3 after every loop and the loop starts with
and the end of the loop is
set volume of 256 to 5
init: untracked pid 123 exited
Whats suddenly worng?
I really dont want to lose my contacts, rest of the apps/tweaks I dont care
Click to expand...
Click to collapse
If u synced your phone with a google account there is no problem for contacts because they will pop up again if you reinstall android and you sync that account again.
Anyway, you can restore system as much as u want because when android start it is read only, so this means that no changes are done to it , simply reinstall android and say "no" when menu ask you to clear data.

I tried like this:
1st Try with Clear Dalvik Cache
2nd Try: Only system reinstall and no DATA wipeout
3rd Try: Reinstall like a hard reset
I change my fonts pretty often and what I think is a ttf was encoded wrong and I replaced that :/

pssshttt! I just rebooted my phone a second time (Power off then back on) and again this stupid error popped error popped up :/
One thing is for sure that its related to the font I am using :s

Endless loop
I have had this endless loop twice and both times I had to reinstall via the installer. I don't know if there is a fix so that you don't need to reinstall. It would be really nice if someone with a little insight could maybe find out what is going on.
I haven't been able to understand exactly what I did to make it loop like this.
I just make sure never to reboot and if so I just hope no looping accours.

There is something with the 3rd Party fonts I used, only one of them caused this, rest all of em were fine. I had to reboot my phone dozen times in order to see stability or corruption before releasing mine build
I think its related to some system related, and happens only when I install that specific cursed font lol

I will continue this topic. I'm using newest froyo on kaiser, newest kernel, and I also have an untracked pid allways, when I'm using my kaiser for longer time, or install something and reboot it. I have no idea what to do with that, and I don't want to go back to WM. Please, help
And sorry for my not good english

I have this problem too,but i didnt use custom fonts only installed opera and tried to move it to sd and installed igo which uses the sd to store files.And then it froze and gave me this piece o .... loop Is there a fix for this?

Reinstall, usually the error is caused by fs corruption.

Tried it but the problem still comes back when i try to install something or try to move something to the sd card.

I have figured out what causes this error and so far it occurs only in froyo ports. The init.rc gets corrupted. The bootup process goes into infinite loop in overwriting the init.rc
Best remedy is to CLEAR DALVIK CACHE and REBOOT. (You often lose your contacts and text msgs and google login details so keep a backup)
Its so much nuisance having this init.rc crashing atleast twice in a day and I am pretty much frustrated with WM either way. I am thinking for replacing my phone for a native android

I had this happen to me 3 times today, recovered all 3 times.
Running Liqid's kernel .32 using ATools and a deodexed version of "system froyo".
Fairly "stock" settings in ATools and only added 4 apps to original build.
I also got "low on space" notifications with each of these crashes. Checked memory after recovery and it was back to normal.
I really need to figure out how to make a sig...lol.

dark_prince said:
Its so much nuisance having this init.rc crashing atleast twice in a day and I am pretty much frustrated with WM either way. I am thinking for replacing my phone for a native android
Click to expand...
Click to collapse
Agreed. Almost there.

same thing happened to me

[BUILD] **Complete FroYo Bundle** FRX07.1 - Maintenance Release

FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>​
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.

Caveats:​
BT - works! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
Audio stutters every 10sec. The only fix I've heard is using a kernel from G3rmo (unfortunately it is old), or
Code:
su
kill -9 28
Which kills the [battery] process. I'm sure this will have negative effects on the battery meter/battery life...
SD Card not working...? "Waiting for SD Card" appearing on boot...? Try putting this command in your startup.txt
Code:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
See gummbah30's post reminding us of these commands.
SD Card has partitions? (If you used a non-XDAndroid build the answer is YES) Then you need to add "no_partitions" to your startup.txt. Between the quotes on the set cmdline line. Do not put it on its own line, it goes in between the quotes! Make sure there is one space between each item.
Front buttons messed up/wrong? You can use my rootfs which incorporates g3rm0's layout. This custom rootfs is no longer necessary, I have committed the changes so you can use the autobuild rootfs (in conjunction with physkeyboard=blac in your startup.txt)!
Keyboard tiny/unusable? Either change the IME (long press on the input box) Get rid of it! I've heard "Hackers Keyboard" is a good alternative - many options. There's also "Better Keyboard", Swype, etc... Side load the APK using AndroidApps, adb install, etc.

stinebd's Changelog:​
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call keya has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse
Layman's Changelog​
(As in, the changelog I wrote )​
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup

Cool man! Thanks for your work.

Thanks!
Well, in fact WEP works perfectly for me. The only thing that wifi fails is at turning it on after turning it off 2 times...
Also, with latest updates I can pair BT, haven't tried to transfer anything.

Eodun said:
Thanks!
Well, in fact WEP works perfectly for me. The only thing that wifi fails is at turning it on after turning it off 2 times...
Also, with latest updates I can pair BT, haven't tried to transfer anything.
Click to expand...
Click to collapse
Ah, I forget how different the bugs are for the TI chipsets. I'll change it, thanks!

Updated to FRX07! Enjoy!

woo FRX07 - I should really update my blackstone as its running 05 still

It seems that the 20110716 Kernel is giving problem to the Blackstone/Topaz.
you may use the previous kernel, or wait until is fixed.
Brgds

mass storage not connecting......anyone else facing this problem?

welard said:
mass storage not connecting......anyone else facing this problem?
Click to expand...
Click to collapse
USB mass storage has never worked (on looped mounts).
You can kinda fake it with Droid Explorer, it uses ADB to 'fake' USB mass storage.

arrrghhh said:
USB mass storage has never worked (on looped mounts).
You can kinda fake it with Droid Explorer, it uses ADB to 'fake' USB mass storage.
Click to expand...
Click to collapse
ok thanks alot....

Had to use a different kernel as yours wouldnt let it boot up
Working:
installing apps, no fc, its connecting to wifi nicely, only dropped once so far, connected to google account fine, coping nicely with downloading and installing multiple apps!!! i like that the others i have tried freeze up
Defect list:
Power control wigit loads frame but not icons on first load
froze when opening camera the second time had to battery pull! on first load
On restart attempt seemed to load haret ok, boot speed and time impoved compaired to first load, still lightly juddering boot animation
On second boot reloaded power control wigit, now displays correctly
Downloading and installing two apps at once navigating home screens caused 20second freeze up.
As someone said the motions but not the workings for usb connection, i cant get droid explorer to see my device so :-(
BT is reallly messed up using app "bluetooth file transfer", just loops itself to death, killings wi-fi as well, not kwl
Using phones bluetooth in settings, my computer says unable to send blah blah then when i turn off bluetooth the wifi is dropped might be connected
Can i overclock stably with this mod?
How do i get the front facing camera working?

FRX07 with CWM
I just succeeded in starting FRX07 as a CWM build.
But the startup wizard seems to be a little bit crazy. It's my first try to make a CWM build, so no wonder there are problems.
If I really can make a stable build I will post the results here.

alphecca911 said:
Can i overclock stabley with this mod?
How do i get the front facing camera working?
Click to expand...
Click to collapse
I couldn't really follow you post, these were the only questions I could find..
You can overclock - stably, dunno. I don't, so you tell me if you can OC.
Front-facing cam doesn't work, kernel issue not build.
ThaiDai said:
I just succeeded in starting FRX07 as a CWM build.
But the startup wizard seems to be a little bit crazy. It's my first try to make a CWM build, so no wonder there are problems.
If I really can make a stable build I will post the results here.
Click to expand...
Click to collapse
Startup wizard...? There isn't a startup wizard on XDAndroid builds...

yes i am sorry for that, i have just been note taking as i have been instaling and testing in the event that someone came, they could assist. I have it up and running now but it didnt work using ur kernel. (wouldnt boot) i have listed defects so far.
Thankyou for your answers to my questions.
Great rom, best i have tried

alphecca911 said:
yes i am sorry for that, i have just been note taking as i have been instaling and testing in the event that someone came, they could assist. I have it up and running now but it didnt work using ur kernel. (wouldnt boot) i have listed defects so far.
Thankyou for your answers to my questions.
Great rom, best i have tried
Click to expand...
Click to collapse
Hrm. I've heard BLAC doesn't work on the newest kernel... I'll have to ask emwe, he had a list of changes for FRX07 release, but I assumed they were RHOD-only... Perhaps something is effecting BLAC that isn't supposed to be .
I don't have a BLAC, so you'll have to help me - what is the newest kernel that does work? 20110711_082424? Also, how far does it get in the process? If adb is up, logs would be appreciated. Thanks.

Allright I'm running into problems! Haret starts and I get as far as the linux boot animation, but then the phone crashes and reboots... anyone else experiencing this?

bdacier said:
Allright I'm running into problems! Haret starts and I get as far as the linux boot animation, but then the phone crashes and reboots... anyone else experiencing this?
Click to expand...
Click to collapse
Sorry mate, seems the newest kernel isn't BLAC friendly! Please tell me which kernel does work... Use the autobuild service and try older kernels. First post has details on how to change your kernel, plus links to autobuild service...
To alphecca911 - most of your issues seem to be first boot related. Remember, you should let it sit on first boot so all the processes that run on first boot have plenty of time to work! I usually let it sit until it sleeps. I've had a lot of weird issues trying to do too many things on first boot on the device... I am impatient just like you probably . Just fight it .

Startup wizard...? There isn't a startup wizard on XDAndroid builds...
Click to expand...
Click to collapse
That might explain a lot
I just checked the system/app folder in the frx07 package. Of course you're right. I copied apps into this without looking. And there was an old SetupWizard.apk.
But just in the moment I started frx07 without any error.
Now I can start to make a real nice package for CWM. And "most" important: try a different boot animation.
I have to thank all XDAndroid developers for this and arrrghhh here for pointing me to it with his posts.
Really great job you are doing here at XDA developers
Thanks

[SOLVED in 2.3.6] Gingerbread 2.3.5 JQ3/JQ4 (soft) reboot issues (random + MicroSD)

UPDATE: [SOLVED] Looks like the GingerBread 2.3.6 ROM fixed this issue.
When the MicroSD card is scanned at startup (i.e. the card is already inserted when the device starts), the MediaScanner / PackageManager analyses the card and this seems to generate a deadlock within the system_server process (.ServerThread), which results in a soft reboot. I don't know if this happens only when there are Apps2SD files (I didn't test this particular edge-case).
So, quite simply, I just insert the MicroSD card once the device is completely booted
UPDATE: sometimes the reboot occurs in this case too, so the deadlock is not completely unavoidable. However, if I long-press the search button, the system doesn't respond which generates a Force Close popup dialog for "Android System" => if I force-close this process, then the device starts responding again and everything works as normal!
Additional note: the MicroSD is perfectly stable when connected in USB transfer mode.
----------
Stock JQ3 has been rebooting randomly on my Tab (no obvious error message in logcat, disabled overclocking/undervolting, Koxudaxi or Overcome kernels, RFS or EXT4 filesystem)...sometimes I can use the Tab for days without problems, but today it keeps rebooting (with or without any interaction from my part).
UPDATE: confirmed with JQ4 too.
The logcat reveals that the watchdog detected a
system-process deadlock, and forced a full restart of the Android
runtime. Here's what [/data/anr/traces.txt] says for .ServerThread (system_server):
Code:
"android.server.ServerThread" prio=5 tid=10 SUSPENDED
| group="main" sCount=1 dsCount=0 obj=0x4050fc58 self=0x2f34a8
| sysTid=12309 nice=-2 sched=0/0 cgrp=default handle=3093984
at java.util.HashMap$HashIterator.hasNext(HashMap.java:~791)
at java.util.AbstractCollection.toArray(AbstractCollection.java:356)
at com.android.server.PackageManagerService.getInstalledPackages(PackageManagerService.java:2385)
at android.app.ContextImpl$ApplicationPackageManager.getInstalledPackages(ContextImpl.java:2186)
at com.android.server.BackupManagerService.allAgentPackages(BackupManagerService.java:966)
at com.android.server.BackupManagerService.addPackageParticipantsLocked(BackupManagerService.java:874)
at com.android.server.BackupManagerService$1.onReceive(BackupManagerService.java:836)
at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:709)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at com.android.server.ServerThread.run(SystemServer.java:673)
"android.server.ServerThread" prio=5 tid=10 SUSPENDED
| group="main" sCount=1 dsCount=0 obj=0x4050fc58 self=0x2f34a8
| sysTid=12309 nice=-2 sched=0/0 cgrp=default handle=3093984
at java.lang.String.compareTo(String.java:~60)
at java.util.ComparableTimSort.mergeLo(ComparableTimSort.java:650)
at java.util.ComparableTimSort.mergeAt(ComparableTimSort.java:447)
at java.util.ComparableTimSort.mergeCollapse(ComparableTimSort.java:370)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:178)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:142)
at java.util.Arrays.sort(Arrays.java:1974)
at com.android.server.PackageManagerService.getInstalledPackages(PackageManagerService.java:2388)
at android.app.ContextImpl$ApplicationPackageManager.getInstalledPackages(ContextImpl.java:2186)
at com.android.server.BackupManagerService.allAgentPackages(BackupManagerService.java:966)
at com.android.server.BackupManagerService.addPackageParticipantsLocked(BackupManagerService.java:874)
at com.android.server.BackupManagerService$1.onReceive(BackupManagerService.java:836)
at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:709)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at com.android.server.ServerThread.run(SystemServer.java:673)
More information here:
http://www.google.co.uk/search?q=reboot+Sending+signal+WATCHDOG+KILLING+SYSTEM+PROCESS

I got reboot whenever I enable wifi.
Hadn't test anything more than this.
Reverse back to dxjpj asian rom

Yes, I realized Wifi would potentially be the cause of the problem, so I am in "flight" mode with both wifi and cellular off.

This is clearly a "system_server" reboot (i.e. the adb connection via USB to my laptop remains alive), so I can capture the system logs even whilst the system is rebooting. Here's some info I found in a mailing list:
Code:
Runtime restarts are almost always for one of two reasons: either a
component running in the system_server process has crashed outright,
or something has caused the system_server's process primary looper
thread to deadlock. The deadlock case is announced by a line in the
logcat buffer reading something very like this:
04-04 14:06:16.888 885 1089 W Watchdog: *** WATCHDOG KILLING SYSTEM
PROCESS: null
I'm going to talk about the NON-deadlock cases first; they're simpler
to diagnose: just look in the logcat trace for the messages about the
system process crashing. There will be a Dalvik stack trace there to
the point at which the fatal exception was thrown, and you then know
where to go looking for the bug. As always, the event log and the
primary text log contain different information; both are useful for
reviewing the state and activity of the device leading up to a crash.
If the crash *was* due to a deadlock, things get a little interesting.
When the watchdog declares a deadlock and forcibly kills the system
process, it first captures the current stack trace of every
system_server process thread into the usual ANR stack trace file
(/data/anr/traces.txt on most devices). This file is automatically
included in a bugreport -- yet another reason to pull a full bugreport
rather than just logcat.
Look at the timestamp of where the watchdog declared a problem. In
the example line I gave above, it was 04-04 14:06:16.888. That tells
you which set of stack traces you're interested in within the "LAST
ANR" section of the bugreport. Find the system_server stack dumps
that were captured at the time of the watchdog's message. For
example, in the bugreport that my example came from, the "LAST ANR"
section was headed:
------ VM TRACES AT LAST ANR (/data/anr/traces.txt: 2011-04-04 14:06:14) ------
and the file holds *two* sets of system_process stacks. One of them
starts like this:
----- pid 885 at 2011-04-04 14:05:42 -----
Cmd line: system_server
and the second starts like this:
----- pid 885 at 2011-04-04 14:06:12 -----
Cmd line: system_server
Note that the first was taken 30 seconds before the second, and the
second was just a few seconds before the watchdog message about
killing the system process to restart the system. The watchdog takes
a thread snapshot after 30 seconds of the looper being unresponsive,
then another snapshot after a full minute of unresponsiveness; and
it's after that full minute that it declares the deadlock and restarts
everything. You probably want to start with the later thread stacks,
the ones that reflect the state of affairs when the watchdog finally
gave up.
In most Android applications the primary looper thread is called
"main", but this is *not* true of the system_process. The primary
system_process looper thread is titled "android.server.ServerThread".
Find that thread's stack trace that was taken at the time the watchdog
declared the deadlock, and you'll be off and running as far as
diagnosing what has caused that looper thread to be unresponsive for >
60 seconds.
At this point you've got the information you need to figure out what
locks are being contended for, what unapproved long-running operations
might be mistakenly being run on the system process's main looper,
etc. Dalvik's stack dump output is very useful, especially since it
tells you things like which other thread currently holds a lock being
requested.

Finally, so it's not my custom rom that cause random reboots to some users.
The strange thing is that not everyone get this issue, me for example, have not none a reboot since i've flashed it.
Daniel, did you have this problem in pure stock jq3?
Meant without overcome kernel installed.
Anyway, you should have this issue with jq4 too, since there are less differences between both versions.

daniel.weck said:
I'm not sure how to Heimdall-flash the JQ4 PDA tar over the ext4 partition? (since I installed Overcome, which aggressively converted /system and /data from RFS to EXT4 without any user-prompt).
Click to expand...
Click to collapse
Ok, that was simple: I flashed [factory.rfs] from JQ4 using Heimdall without repartition (and with the usual PIT file), and on reboot the Overcome kernel automatically converted to EXT4 once again (a short 2 minutes process, as my /data partition had already been converted before). The APKs are now being Odex'ed (Dalvik cache reset)...waiting...
I hope this will fix the reboot issue. UPDATE: no

af974 said:
Finally, so it's not my custom rom that cause random reboots to some users.
The strange thing is that not everyone get this issue, me for example, have not none a reboot since i've flashed it.
Daniel, did you have this problem in pure stock jq3?
Meant without overcome kernel installed.
Anyway, you should have this issue with jq4 too, since there are less differences between both versions.
Click to expand...
Click to collapse
As soon as I installed stock JQ3, I had a couple of reboots, however the ROM "became" stable rapidly and I enjoyed using the Tab for a number of days without any major issues. All this time, I was using Koxudaxi's build (overclocked, undervolted). Today, I updated some apps using the Market, I launched ezPDF and the system then entered this reboot frenzy! I went into flight mode to eliminate potential wifi/radio issues, I removed the overclocking/undervolting, and finally I switched to the Overcome kernel (just to try something different)...to no avail.
I have now flashed JQ4 [factory.rfs], but the system is rebooting again. Frustrating!!
I'm going through /data/anr/traces.txt again, hoping to find the culprit...

I was running stock froyo for the longest time, almost a year. I had huge problems with random reboots. Typically two-three days with frequent reboots followed by a week or two with few or no reboots.
I related the reboots mostly to two different things.
One was sim related and even though I had a new simcard I eventually had to get a new. I've also read about other tabowners with similar problems so maybe tabs are "simsensitive". With the new simcard, this problem went away.
The other problem was with wifi.
The easiest way to make my tab find my wireless quickly, was to put it into flightmode and back on again immediately. In 30-40 percent of the cases this would cause it to crash and reboot. After the reboot everything was fine again.
A month ago I finally dared to flash and I've been on the latest Overcome for a month now. I've had just a single random reboot in this time.
Just my two cents...

The issue appear indeed in the two versions of the ROM, the jq4 also have this issue and tweaking the build.prop does not change it, af974 I've try you're patch but still the issue remains, what is weird is that I spend the last 10 hours on wifi with no reboot and this morning, boom, reboots... the networks is not the same but still...

SOLVED.
UPDATE: [SOLVED] the reboots stop once the MicroSD card is removed from its slot. I have also tried to remove the SIM card. As soon as the SD card is inserted, the Apps2SD applications are analysed by the Nazca/Media Scanner and from this point onwards the Package Manager sub-system goes crazy. I will restore my apps on the device, and I will format the MicroSD, again... I doubt it is a problem with the Micro-SD hardware itself, more like a driver issue. It seems quite common with mobile phones, all brands concerned.

Nice one Daniel,
let us know how it goes after some test in the meantime i'll point my users to here.
daniel.weck said:
UPDATE: [SOLVED] the reboots stop once the MicroSD card is removed from its slot. I have also tried to remove the SIM card. As soon as the SD card is inserted, the Apps2SD applications are analysed by the Nazca/Media Scanner and from this point onwards the Package Manager sub-system goes crazy. I will restore my apps on the device, and I will format the MicroSD, again... I doubt it is a problem with the Micro-SD hardware itself, more like a driver issue. It seems quite common with mobile phones, all brands concerned.
Click to expand...
Click to collapse

Additional note: the MicroSD is perfectly stable when connected in USB transfer mode.

I made a selective backup of important stuff from [/sdcard/external_sd/] (whilst in USB data transfer mode with my laptop), making sure to copy all the [*.asec] App2SD files from [/sdcard/external_sd/.android-secure/]. Then I formatted the MicroSD card on my laptop, and formatted again from the tablet as it detected a corrupted/damaged card (I suppose the FAT driver on the tablet is picky). I then copied the [*.asec] files back to [/sdcard/external_sd/.android-secure/] (several megabytes which I am happy not to have to download again via the Market), and the Package Manager seems pretty stable so far. Win!
I haven't put the SIM card back in yet, first I am updating my Titanium backup!
Cheers, Dan

When the MicroSD card is scanned at startup (i.e. the card is already inserted when the device starts), the MediaScanner / PackageManager analyses the card and this seems to generate a deadlock within the system_server process (.ServerThread), which results in a soft reboot. I don't know if this happens only when there are Apps2SD files (I didn't test this particular edge-case).
So, quite simply, I just insert the MicroSD card once the device is completely booted

daniel.weck said:
When the MicroSD card is scanned at startup (i.e. the card is already inserted when the device starts), the MediaScanner / PackageManager analyses the card and this seems to generate a deadlock within the system_server process (.ServerThread), which results in a soft reboot. I don't know if this happens only when there are Apps2SD files (I didn't test this particular edge-case).
So, quite simply, I just insert the MicroSD card once the device is completely booted
Click to expand...
Click to collapse
I don't use App2sd so maybe that's why I don't have reboots with Gingerbread.
There are actually people who think that I with my SG Tab am jealous of their ipads. Moahaha!

What I did.....
What I did, when I first read this thread, I removed my SD-Card and formated it adapted to my PC (FAT32).
Next I reincerted it to my Tab. Til now (32 hours) it didn't reboot an single time:
I can check this, because of my Plantronics Discovery 975 BT headset that is permanently connected to the Tab.
Whenever in the past the Tab did a soft reboot (JQ3) it was hard work to get the headset reconnected.
PS: Used wifi for about two hours today. Seems to by stable for now. Will push some apps2sd and so on to see if it takes over rebooting.

Unfortunately I doubt this is the solution, the reboots remain even when I remove my sdcard...

CarpeNoctem said:
Unfortunately I doubt this is the solution, the reboots remain even when I remove my sdcard...
Click to expand...
Click to collapse
UPDATE: sometimes the reboot occurs even when I insert the MicroSD card after boot, so the deadlock is not completely unavoidable. However, if I long-press the search button, the system doesn't respond which generates a Force Close popup dialog for "Android System" => if I force-close this process, then the device starts responding again and everything works as normal!

daniel.weck said:
UPDATE: sometimes the reboot occurs even when I insert the MicroSD card after boot, so the deadlock is not completely unavoidable. However, if I long-press the search button, the system doesn't respond which generates a Force Close popup dialog for "Android System" => if I force-close this process, then the device starts responding again and everything works as normal!
Click to expand...
Click to collapse
Not really satisfying!
CarpeNoctem said:
Unfortunately I doubt this is the solution, the reboots remain even when I remove my sdcard...
Click to expand...
Click to collapse
Yes, same with me. Really annoying.
And by the way: android browser task often crashes, when trying to open an additional tab.

Oh damn, i really would like to have too this annoying bug.
In % , this happens in what situations? Browsing, wifi, any addictional info please.
Could someone with this bug post a logcat? Dowload alogcat from market, enable to view only errors and export the log, i don't have any reboots but my log show many errors regarding mtp, keyboard and sensor.

[24-feb-2012] ElocityPlusMod v1.00 (A7 PLUS ONLY)

!!This is ONLY for Elocity A7 PLUS! (model with 1024x600 resolution)
This Mod is based on Elocity Stock with additions from Nvidia SDK, to make a better functioning stock rom with google apps.
You can also follow updates on my homepage at Dexter's mods
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE
You can download from here MD5SUM: 7d69789e85e946c7f456c8f8f455a352
It will require Wipe/factory reset as well. as reports on the update seems to report some problems if not, so its your ownproblem if it does FC alot, if you do not wipe
Install using recovery menu.
copy the file to the root of your sdcard and rename to Update.zip.
Enter "Recovery menu" by pressing power for 2seconds, release
then hold power button until "hold power 5sec...." appear and wait until it says booting recovery kernel..and release power button.
Press "HOME" button to see menu, use SEARCH/BACK button to navigate.
select "Wipe/factory reset" - press MENU key to activate
then select "apply sdcard:update.zip" - press MENU to activate
after the small install process - press "reboot" to finalize and wait for the upgrade to take place on second screen that appear.
ISSUES
- Screen brightness cannot change (Settings crash when selected)
- Volume in status bar not included (using old A7 mod here, ill figure a solution out, maybe app from Market?)
KERNEL USED IS STOCK ROM EDITION, SINCE SOURCE IS NOT RELEASED
CHANGELOG
v1.00
- Initial release
- includes a fixed RECOVERY , which allow you to do a proper WIPE (Factory reset)
- DSP audio manager
- rotation fix for some games
- all google apps functionality with calendar and email and sync
- flash player 10.3 included (full embedded media support) , if you want to upgrade, please uninstall the old one first.
- still no "move 2 sdcard" (needs different release 2.3.6 to support it and new kernel)
- no longer uses /storage as sdcard location.
/mnt/sdcard is now internal storage,
AND
/mnt/sdcard/sdcard-disk is external sdcard location.​- root enabled (Superuser is used here)
- wma/wmv media support​
THANKS to all who donated previously and up to now! its appreciated, and shows that people like the extras added...
WARNING: Use this image at your own risk and i take no responsibility if you brick your tablet..
PS: you can ALWAYS use the elocity Recovery from A7 install instructions here
If you like it press "THANKS"

reserved for future.

Bro plzz check ur pm box

Need ur help Dexter...

hey dexter need ur help...... ive tried porting sense 3.5 to defy......when i went in the port section in kitchen.........i setup the port and i got 2 folders MY KERNEL,MY DEVICE FOLDER....i am porting it on defy...i changed the folder MY DEVICE FOLDER to "WORKING_sense" and then set up a working folder and then built up the rom but it didnt work out...i got an error
E:error status 6...wat shud i do..plzz help

hey bud my usb does not work on this mod also is there a honeycomb for the plus version

gemini002 said:
hey bud my usb does not work on this mod also is there a honeycomb for the plus version
Click to expand...
Click to collapse
usb stick works fine here? and shows in "storage" when mounted.b

Dexter_nlb said:
usb stick works fine here? and shows in "storage" when mounted.b
Click to expand...
Click to collapse
weird soulution then?i tried to flash again but same thinh..maybe i will put orginal sofware then update again

gemini002 said:
weird soulution then?i tried to flash again but same thinh..maybe i will put orginal sofware then update again
Click to expand...
Click to collapse
did you note, mount location changed from original rom?`its no longer in /mnt/storage but /mnt/sdcard like other tablets.

when i plug it in its not detected does not light up..i flashed orginal software and port works
---------- Post added at 09:04 PM ---------- Previous post was at 08:45 PM ----------
when i install ur rom @ first boot i get boot loop so i have to turn off then it boots but no working usb port so frustrated
---------- Post added at 09:42 PM ---------- Previous post was at 09:04 PM ----------
Dexter_nlb said:
did you note, mount location changed from original rom?`its no longer in /mnt/storage but /mnt/sdcard like other tablets.
Click to expand...
Click to collapse
yes usb is not bein mounted at all

The latest fw was on my tablet also on orginal fw in recovery when I choose factory reset it just shuts of ..
Sent from my HTC EVO 3D X515m using XDA App

gemini002 said:
The latest fw was on my tablet also on orginal fw in recovery when I choose factory reset it just shuts of ..
Click to expand...
Click to collapse
you need to install my version, and then go back into recovery and you see recovery name is changed, and now factory reset would work fine.

yes works fine now ..sometimes sceen turns off and wont turn back on reboot needed also when will update to this come out wnt to move apps 2 sd

gemini002 said:
yes works fine now ..sometimes sceen turns off and wont turn back on reboot needed also when will update to this come out wnt to move apps 2 sd
Click to expand...
Click to collapse
the SOD issue was a well known problem of Tegra2 in its early days. problem with this tablet is that it needs a new kernel update and i do not see that one coming to solve SOD problems (from the past).
strangely the first A7 did not have it,while my Folio100 suffered badly from SOD with the early kernels.
so its known, but not being fixed i guess.
actually Nvidia wrote on their webpage that this hardware had the problem on some tablet could be awakened again by pushing out the sdcard? maybe an idea?

u have made this tablet a rel steal for me now only paid 120 cdn for it...now how can we get tablet to install to sd card?

gemini002 said:
u have made this tablet a rel steal for me now only paid 120 cdn for it...now how can we get tablet to install to sd card?
Click to expand...
Click to collapse
we need a kernel, the function required for installing to sdcard (loopback device) is not compiled into the kernel. so its not working for any rom.
i made CM7 + HC3.0(from A7Comb) working, but without the function from the kernel, those are not worth using. so im holding back those for a release until a solution is found.

Dexter_nlb said:
we need a kernel, the function required for installing to sdcard (loopback device) is not compiled into the kernel. so its not working for any rom.
i made CM7 + HC3.0(from A7Comb) working, but without the function from the kernel, those are not worth using. so im holding back those for a release until a solution is found.
Click to expand...
Click to collapse
Does it have more internal memory free??would love to try it ..also how dani increase my internal memory

gemini002 said:
Does it have more internal memory free??would love to try it ..also how dani increase my internal memory
Click to expand...
Click to collapse
you can find the CyanogenModPlus edition now using link in post to download.
its beta but until a kernel is ready, we have to live with minors. as its work quite well.
remember to have embedded video working, install the CF3D plugin from Market (ChainFire 3d) and reboot, and you can see embedded video quite fine on cyanogenmod too.

Hey Dexter_nlb,
This seems to be the best rom available for this tablet - its more stable then the stock roms and offers some improvements and speed overall making it the best so far.
I just have one problem with it that you might be able to help out with:
I have just noticed that your ROM is missing the ability to change the WIFI Sleep Policy. Its set for ON by default - but cannot be turned off. This is a big problem as WIFI disconnects every time the screen turns off. It then takes over 30sec to re-connect (depending on wifi network) and any programs open that require a connection stop responding or start to force close.
I use my Tablet as a controller for my home theater and because of this I cant use this great rom. I cant use the stock rom either as The stock rom does not work with my home theater apps.
I was wondering if you could fix this easily or could show me how - EG: Build.prop string??? or other mod? - port settings.apk or wifi related libs from std rom?
I just need the WIFI to stay on.
Thanks in advance.
JF

JF-GINO said:
This seems to be the best rom available for this tablet - its more stable then the stock roms and offers some improvements and speed overall making it the best so far.
Click to expand...
Click to collapse
i would dare say its the only one for A7+ now
activity has changed alot since all the new android tabs got out.
JF-GINO said:
I just have one problem with it that you might be able to help out with:
I have just noticed that your ROM is missing the ability to change the WIFI Sleep Policy. Its set for ON by default - but cannot be turned off. This is a big problem as WIFI disconnects every time the screen turns off. It then takes over 30sec to re-connect (depending on wifi network) and any programs open that require a connection stop responding or start to force close.
I use my Tablet as a controller for my home theater and because of this I cant use this great rom. I cant use the stock rom either as The stock rom does not work with my home theater apps.
I was wondering if you could fix this easily or could show me how - EG: Build.prop string??? or other mod? - port settings.apk or wifi related libs from std rom?
I just need the WIFI to stay on.
Click to expand...
Click to collapse
you might be able to download an app from Market that solves it?
Advanced WIFI LOCK (Free edition)
it might help.
otherwise only way around is going into Development settings, and chose "stay awake"?
anyways, the wifi issue is more common being a kernel issue, which in the early nvidia for these tablets had a deep sleep issue, which also killed wifi signal. its only solved by a full kernel upgrade to android 3.x (2.6.36.x or higher) which i have no good chance of doing completely.
to get better support, the CyanogenModPlus rom is getting better now, since kernel is changing with OC support and better market install support as well.
but thats probably the best this can offer for now.