Related
The buildbot has started building the Cm6 nightlies again. Which is awesome for those of us that like to test the latest CM fixes/features.
Problem is the kernel or boot is whacky.
So make a
nandroid of your RC3 and then
wipe/flash nightly
advanced nandroid restore and restore the BOOT: from your RC3.
Cyanogenmod specific forums have a nightly discussion going as well.
http://forum.cyanogenmod.com/topic/3579-nightlies-discussion-of-nightlies/
thanks for the boot tip man, I couldn't get it loaded.
Anything noticably different?
Good call dood, thanks for the tip. I'm wondering if PSX4Droid is working on the latest Nightlies as it was working on old Nightlies but not on RC3. Not sure what this is related to. But I'll try it and report back, if anyone else is wondering.
Thanks!
Funkwheat said:
Good call dood, thanks for the tip. I'm wondering if PSX4Droid is working on the latest Nightlies as it was working on old Nightlies but not on RC3. Not sure what this is related to. But I'll try it and report back, if anyone else is wondering.
Thanks!
Click to expand...
Click to collapse
Do hydra/king kernels still cause lock up
Sent from my ADR6300 using XDA App
Confirmed psx for Droid works with nightly.
Sent from my Incredible using XDA App
TrailBlazer31 said:
Confirmed psx for Droid works with nightly.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Hmmm.. It's not working for me.
Edit: Nevermind, yes it is. =P
Freakin' sweet! Audible works now
Anyone test sling player?
-Sent from your mom's phone.
updated power control widget is perfect. Also noticed when I hold down power and choose reboot there are options to go right into recovery from there. Pretty sweet, don't recall that in RC3 ?? (or did I miss it?)
Bluetooth audio still doesn't stream with my car radio though (all other 2.1 and 2.2 roms do so fine). Although I wonder if we need to wait for one that actually boots with it's own boot.img?? Isn't the kernel in there?
Any updates regarding emmc?
Sent from my ADR6300 using XDA App
Has the latest nightly addressed the choppy bluetooth audio?
I could not get past the white 'htc inc' screen. Is s-off required?
Sent from my Incredible using Tapatalk
read the first post
BlazeD OnE said:
read the first post
Click to expand...
Click to collapse
Sorry and thx!
Sent from my Incredible using Tapatalk
no need for apologizes, and your welcome
8-23 is on rm
So, what's up with the browser FCs? Any better?
JC
hydrored said:
8-23 is on rm
Click to expand...
Click to collapse
oh snape!
**EDIT**
BOOT is still b0rked for me so looks like we still have to adv restore it from RC3.
if you advanced nandroid restore your BOOT then you will be ok
the kernel is whacked
I need some help figuring out why my camcorder force closes. I'm running CM7. I've tried wiping everything and re-flashing, clearing the camera data, fixing permissions, and searching the forums. Everything else works. When I try to use the camcorder it will force close, then my phone will reboot a short time later.
Try to uninstall the camera.apk and replace it with this one see if that works http://db.tt/dMMC8sj
I hope it works for you
Sent from my Nexus One using XDA App
paco909 said:
Try to uninstall the camera.apk and replace it with this one see if that works http://db.tt/dMMC8sj
I hope it works for you
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
No dice. The same thing happens there.
Did you update your Google addon also do you have the recommended HBOOT for cm7
Sent from my Nexus One using XDA App
paco909 said:
Did you update your Google addon also do you have the recommended HBOOT for cm7
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I have the latest Gapps and the HBOOT I have is 0.35.0017.
What build are you running of cm7
Sent from my Nexus One using XDA App
paco909 said:
What build are you running of cm7
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The latest Fits one. This has been happening early on though. There has to be something different with my phone compared to everyone else running the same ROM because the camcorder works for them. Maybe I need a different kernel.
The kernal that I'm running is 2.6.37-cyanogenmod-01117-g3687213 [email protected] #1
Sent from my Nexus One using XDA App
paco909 said:
The kernal that I'm running is 2.6.37-cyanogenmod-01117-g3687213 [email protected] #1
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
That's what I was running, then I switched it to Redstar's. I don't know, obviously. My plan right now is to wait until RC1 comes out or a Fits build with more features and then flash back to stock and redo everything. I hope I don't have to, but I'm out of ideas.
Can anybody else offer some advice before I start wiping everything again?
Camcorder will freeze, then the phone reboots.
I've tried formatting the boot, system, data, cache, then flashing again. I've tried clearing the camera data. I've tried uninstalling the camera and reinstalling it.
I'm on RC1 of CM7, the latest HBOOT, and the kernel that comes with CM7.
i have the same issue tried switching kernels to no avail.
Count me in !
I did not build this rom, I just swapped out the power profile from a stock GB rom to fix the battery drain and overheating issue and added the file to allow it to boot in safestrap3.
All thanks goes to Team Liberty for the rom and Hashcode for safestrap3 and to Endoroid for reminding me what to do to fix battery drain.
http://db.tt/1G3IfKXy
See original Liberty3 V2.0 original thread here http://forum.xda-developers.com/showthread.php?t=1366882
Sent from my DROID3 using XDA
Nice! Will definitely give this a spin.
Let's give it a try.
Thanks for the effort, man!
Sent from my XT860 using xda app-developers app
Jason Roach said:
I did not build this rom, I just swapped out the power profile from a stock GB rom to fix the battery drain and overheating issue and added the file to allow it to boot in safestrap3.
All thanks goes to Team Liberty for the rom and Hashcode for safestrap3 and to Endoroid for reminding me what to do to fix battery drain.
Click to expand...
Click to collapse
Super! Thanks, I was thinking about doing the same when I saw the posts in the other thread but didn't get around to it. I appreciate the effort.
Munckster said:
Let's give it a try.
Thanks for the effort, man!
Sent from my XT860 using xda app-developers app
Click to expand...
Click to collapse
doogald said:
Super! Thanks, I was thinking about doing the same when I saw the posts in the other thread but didn't get around to it. I appreciate the effort.
Click to expand...
Click to collapse
No problem folks. its the least i could do for all the years ive been d/l stuff from here lol. i got this working for myself out of bordum the other night and theres no reason to keep this old throwback rom to myself lol.
i hope its working ok for all who try it out, if anyone wants to reupload it somewhere with faster d/l speeds please feel free to do so and i will put the link in the first post.
I keep getting market force closes. I've tried lost of things - wiping data in the market app in settings->applications->manage applications; reflashing the ROM; wiping Dalvik; wiping data and reflashing the ROM and setting up from scratch. No matter what I do, the market FCs.
Anybody else?
doogald said:
I keep getting market force closes. I've tried lost of things - wiping data in the market app in settings->applications->manage applications; reflashing the ROM; wiping Dalvik; wiping data and reflashing the ROM and setting up from scratch. No matter what I do, the market FCs.
Anybody else?
Click to expand...
Click to collapse
I remember something about this. If you can find the original liberty thread (go back like a year) i believe there was a solution found
Sent from my DROID3 using xda premium
---------- Post added at 10:07 AM ---------- Previous post was at 09:40 AM ----------
http://forum.xda-developers.com/showthread.php?t=1366882
Start reading around post 110
Sent from my DROID3 using xda premium
Endoroid said:
I remember something about this. If you can find the original liberty thread (go back like a year) i believe there was a solution found
Sent from my DROID3 using xda premium
---------- Post added at 10:07 AM ---------- Previous post was at 09:40 AM ----------
http://forum.xda-developers.com/showthread.php?t=1366882
Start reading around post 110
Click to expand...
Click to collapse
I read all that last night - also droidforums.net. There was never a solution beyond reflash, and nobody ever reported back if they were able to solve it. I don't recall having this problem with Safestrap 1.08 when I tried Liberty before.
Oh well. I'll keep playing around. I tried the vending.apk from Maverick 4.5 but that didn't seem to help either. I also tried turning ads back on in ROM Toolbox. It may be time to go through build.prop or something.
doogald said:
I read all that last night - also droidforums.net. There was never a solution beyond reflash, and nobody ever reported back if they were able to solve it. I don't recall having this problem with Safestrap 1.08 when I tried Liberty before.
Oh well. I'll keep playing around. I tried the vending.apk from Maverick 4.5 but that didn't seem to help either. I also tried turning ads back on in ROM Toolbox. It may be time to go through build.prop or something.
Click to expand...
Click to collapse
I've used liberty off and on and I only ever had that problem the first time, and never again. Odd
Sent from my DROID3 using xda premium
doogald said:
I keep getting market force closes. I've tried lost of things - wiping data in the market app in settings->applications->manage applications; reflashing the ROM; wiping Dalvik; wiping data and reflashing the ROM and setting up from scratch. No matter what I do, the market FCs.
Anybody else?
Click to expand...
Click to collapse
Ok, I got it working. What worked for me is to skip the initial setup of Liberty by doing the four corner trick (i.e, on the "touch the Droid to begin" screen, touch the four corners of the touchable display in the order upper left, upper right, lower right, and lower left; this will skip the setup steps and bring you straight to the home screen). Touching the market after that asks you to log in to a Google account, and this successfully starts the market/play store without a force close.
Breaking my usual rule of not changing two things at once, I also switched from the first ROM slot to my third (I have three slots.) I doubt that made a difference, though.
doogald said:
Ok, I got it working. What worked for me is to skip the initial setup of Liberty by doing the four corner trick (i.e, on the "touch the Droid to begin" screen, touch the four corners of the touchable display in the order upper left, upper right, lower right, and lower left; this will skip the setup steps and bring you straight to the home screen). Touching the market after that asks you to log in to a Google account, and this successfully starts the market/play store without a force close.
Breaking my usual rule of not changing two things at once, I also switched from the first ROM slot to my third (I have three slots.) I doubt that made a difference, though.
Click to expand...
Click to collapse
Hmm, that could be why. I always skip setup via 4 corners, although back when liberty first came out I probably didn't. Although it could be coincidence, as stated in the thread, it seemed kinda random, appearing for some, and being fixed via multiple reflashing.
I've been giving some consideration to going back to liberty for awhile, switch it up. I'll put it to the test if i do
Sent from my DROID3 using xda premium
I feel the need to point out that I don't use safe strap but plain old cwm+bootstrap. I have no need to keep a stock partition, plus saftedtrsap mounts roms as loop back devices which is slower. Minimoto is much faster when it's actually my /system and not a mounted. Img
Sent from my DROID3 using xda premium
Endoroid said:
I feel the need to point out that I don't use safe strap but plain old cwm+bootstrap. I have no need to keep a stock partition, plus saftedtrsap mounts roms as loop back devices which is slower. Minimoto is much faster when it's actually my /system and not a mounted. Img
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Do you have to change anything to get it to boot in cwm?
Sent from my DROID3 using XDA
Jason Roach said:
Do you have to change anything to get it to boot in cwm?
Sent from my DROID3 using XDA
Click to expand...
Click to collapse
Not a thing
Sent from my GT-P5110 using xda premium
Endoroid said:
Not a thing
Sent from my GT-P5110 using xda premium
Click to expand...
Click to collapse
Nice, thanks for the info
Sent from my DROID3 using XDA
doogald said:
I read all that last night - also droidforums.net. There was never a solution beyond reflash, and nobody ever reported back if they were able to solve it. I don't recall having this problem with Safestrap 1.08 when I tried Liberty before.
Oh well. I'll keep playing around. I tried the vending.apk from Maverick 4.5 but that didn't seem to help either. I also tried turning ads back on in ROM Toolbox. It may be time to go through build.prop or something.
Click to expand...
Click to collapse
I flashed it with safestrap 3.5 and everything works perfect for me. Are you sure you guys used the right gapps? Everything works on my phone.
P.S.......And thanks for updating Liberty to work with Safestrap 3.5..........
Sent from my DROID3 using Tapatalk 2
lotzakritters said:
I flashed it with safestrap 3.5 and everything works perfect for me. Are you sure you guys used the right gapps? Everything works on my phone.
P.S.......And thanks for updating Liberty to work with Safestrap 3.5..........
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
GApps are included
Sent from my DROID3 using xda premium
Endoroid said:
GApps are included
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Oh, cool. I'm just used to flash my own GApps with Liberty, like before.
Weird, not sure why people are having an issue with it then?
Sent from my DROID3 using Tapatalk 2
lotzakritters said:
Oh, cool. I'm just used to flash my own GApps with Liberty, like before.
Weird, not sure why people are having an issue with it then?
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
You only need to flash GApps on aosp based roms like cm and aokp. This is due to legal issues, android is open source, gapps are not. Since liberty is heavily modified blur base rather than being compiled from source, gapps are included.
Sent from my DROID3 using xda premium
lotzakritters said:
I flashed it with safestrap 3.5 and everything works perfect for me. Are you sure you guys used the right gapps? Everything works on my phone.
Click to expand...
Click to collapse
Thanks, I'll have to keep that in mind. I'm not sure if there's anything in a CyanogenMod Gapps that would be bad for Liberty.
Anyway, the four corners trick works, and everything else in setup is easy to re-do. Restoring apps and WiFi access points I do with Titanium anyway, so I don't need to restore from Google.
I have to say that I set this up but went back to Minimoto because I was traveling and I wanted to have a known-good setup. I'll restart with Liberty in a day or two and see how things go.
Question about the lack of menu button.
So before buying the phone I I check into it and found out it used the 3dots and not a menu button like other androids.
Also found the back button long press as menu hack.
I have that install but I am still having problems and got questions.
First what do you do when the app your on doesn't have the 3dots?
Xda app doesn't have it to make a new thread. Also found a few of my older apps don't have it either.
Next the problem.
80% of the time when I press and hold the back button it just goes back. Or it will go back and then open the 3dot menu.
Is there any way to fix this or map the menu to long press home?
Sent from my HTC One using xda app-developers app
You can use Elemental X kernal and have the HTC logo as a menu button that's what I use and it works a treat. Are you on a custom OS as if you are you may have flashed something with the 3dot away mod explaining why you never see it?
Sent from my HTC One using xda app-developers app
snowwhite007 said:
You can use Elemental X kernal and have the HTC logo as a menu button that's what I use and it works a treat. Are you on a custom OS as if you are you may have flashed something with the 3dot away mod explaining why you never see it?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Stock rooted tmobile Rom.
Xposed mod for back button.
And I don't truly like custom kernels. Had problems in the pass and had to update them weekly
Sent from my HTC One using xda app-developers app
xile6 said:
Stock rooted tmobile Rom.
Xposed mod for back button.
And I don't truly like custom kernels. Had problems in the pass and had to update them weekly
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
That kernal is stable and doesn't require updating every week so it's a good option for you
+1 for elemental X. It's great. What about if you download pie control from the play store and set a menu control that way? I used to use the back button method but find it doesn't work half of the time. HTC logo2menu from custom kernels work 100%
Sent from my HTC One using xda premium
If you prefer to avoid custom kernel, then use a Rom based on 4.2.2 as these allow long press home to be enabled for menu
Sent from my HTC One using xda app-developers app
Thanx for the information.
I'll try the pie control for now. And look into the 4.2 Roma and kernel.
I'm so dumb. If you use the hack it hides the menu. Never knew that since I rooted and install the Xposed hack hrs after having the phone.
Sent from my HTC One using xda app-developers app
I'm using tonyp's latest rom build (05) and the Magnyfying Glass (physical button) is not working.
When I push the button nothing happens, Actually the phone vibrates, but doesn't go to the search bar.
Anyone has this issue or know how to solve it?
Thanks!
felzanella said:
I'm using tonyp's latest rom build (05) and the Magnyfying Glass (physical button) is not working.
When I push the button nothing happens, Actually the phone vibrates, but doesn't go to the search bar.
Anyone has this issue or know how to solve it?
Thanks!
Click to expand...
Click to collapse
Do a full wipe and reflash the rom. Dont't forget to backup what you need.
Sent from my LG-P990 using Tapatalk 2
filarod said:
Do a full wipe and reflash the rom. Dont't forget to backup what you need.
Sent from my LG-P990 using Tapatalk 2
Click to expand...
Click to collapse
Reflashing tonyp's rom didn't solve the problem.
Installed CM 10.1 "Stock" and it is solved, button working again and rom running smooth.
try to set it manually in settings / hardware buttons
Sent from my LG-P990 using xda premium