{
"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"
}
Q&A on XDA for 7.1.0
This is just one of the many places you can discuss/chat/argue(nicely)/complain/rant/rave etc. with your fellow G-Tabbers about the latest version of VEGAn-TAB GingerEdition 7.1.0.
You can find all the pertinent info in the developer section here: http://forum.xda-developers.com/showthread.php?t=1236880
And also on the website here: http://vegantab.gojimi.com/2011/08/26/vegan-tab-gingeredition-7-1-0-for-bootloaders-1-1-and-1-2/
Since I will be the only one able to post on the dev section post I have opened up this Q&A post here. This has the advantage of allowing me to update when I can any info in subsequent posts in the Development forum without that post ending up at 100+ pages long...
I will also be closing the old thread so I apologize if anyone's conversation there gets abruptly cut off. Feel free to continue here but do try to stay on topic.
--Enjoy
Reserved
FAQ's Etc.
Q. My Market is no longer showing all the apps/or showing my device as incompatible!!
A. It happens.... sometimes the market loses the proper registration for our device.... to fix and re-register your device with the market... got to Settings/Applications find the Market app under the ALL tab and press the Clear Data button. That's it.... just reopen the market and viola everything is cool again.
I don't know whether this had been asked, although i sure I scoured google search about my problem and had no luck about the result
I had BL 1.2 , and after nvflashing and reinstalling CWM (BL 1.2) , I tried to flash and got this error
asser failed: getprop("ro.product.device =="harmony" || getprop("ro.build.product")
So did I missed anything painfully obvious? Did I need to upgrade this rom from previous VeganGE RC1 ? I previously used clemsyn/calkulin rom v6
fury7 said:
I don't know whether this had been asked, although i sure I scoured google search about my problem and had no luck about the result
I had BL 1.2 , and after nvflashing and reinstalling CWM (BL 1.2) , I tried to flash and got this error
asser failed: getprop("ro.product.device =="harmony" || getprop("ro.build.product")
So did I missed anything painfully obvious? Did I need to upgrade this rom from previous VeganGE RC1 ? I previously used clemsyn/calkulin rom v6
Click to expand...
Click to collapse
I don't think you missed anything. I had JUST installed a fresh clean VeganTab 7.0.0 RC1 (no apps installed yet) and it failed with the same assertion.
I just extracted the updater-script, removed the first two lines, and replaced it. Then it installed correctly.
However I also noticed that the splash screen still says 7.0.0. Also, Google Services framework crashed on first bootup (I wiped after flashing). Worked after the second bootup.
im getting this same error. Can you help explane what you did to get it to work?
New tab user here, so don't be harsh on the noob, can i use this on a Hannspad or not?
Can I get an Amy Pond wallpaper?
fury7 said:
I don't know whether this had been asked, although i sure I scoured google search about my problem and had no luck about the result
I had BL 1.2 , and after nvflashing and reinstalling CWM (BL 1.2) , I tried to flash and got this error
asser failed: getprop("ro.product.device =="harmony" || getprop("ro.build.product")
So did I missed anything painfully obvious? Did I need to upgrade this rom from previous VeganGE RC1 ? I previously used clemsyn/calkulin rom v6
Click to expand...
Click to collapse
Same error here too
Sent from my Adam using Tapatalk
Phoenix84118 said:
I don't think you missed anything. I had JUST installed a fresh clean VeganTab 7.0.0 RC1 (no apps installed yet) and it failed with the same assertion.
I just extracted the updater-script, removed the first two lines, and replaced it. Then it installed correctly.
However I also noticed that the splash screen still says 7.0.0. Also, Google Services framework crashed on first bootup (I wiped after flashing). Worked after the second bootup.
Click to expand...
Click to collapse
So what is the line that you typed in the update script?
AWESOME -- glad to see that VEGAN-Tab GB still lives!
TdiDave said:
im getting this same error. Can you help explane what you did to get it to work?
Click to expand...
Click to collapse
I had this same issue with vanilla CM, at least certain revisions. I could never figure out the why, but i had ripped out the offending lines in my own attempts to get CM7 running. Not sure if that's really recommended or not....
It's an issue with the 1.2 CWM currently released. I will be releasing a new version soon for both bootloaders. This issue is caused by CWM reporting the incorrect board identifier and is an easy remedy. For the time being I have uploaded a corrected installer in the dev section that will overlook the issue for now. It should be available in a few minutes.
So where's the updater script? Noob here T____T
Ok the new download with fixed assert check is available in the dev forum post. Please redownload and report back.
fury7: just redownload from dev section.... new installer should work.
assert(getprop("ro.product.device") == "harmony" || getprop("ro.build.product") == "harmony" || getprop("ro.product.board") == "harmony" ||
getprop("ro.product.device") == "smb_a1002" || getprop("ro.build.product") == "smb_a1002" || getprop("ro.product.board") == "smb_a1002");
This is what is in the first 2 lines, im no programer so have little understanding of what im looking at, but comparing it to other build props this looks like it labeling the device 2 different things, all other only did one ???
Edit: now downloading the file with corrected assert
Installed, wiped data ect. Every things is working great. Thanks
Just installed over clean/cleared stock 1.1, works great. All apps appear in market. No fc's yet.
One problem. Pandora, every other song plays back at a wonky slow speed. Sounds like playing a record at the wrong speed. Could this be related to dspmanager issues in CWM??
Can anyone repro this?
I can confirm this issue..... it's not related to dsp stuff because I remove all of that code as it is not functioning properly. I will look into it... it has something to do with aac decoder.
WIFI issues anyone?
I'm able to connect successfully to my Wifi network (protected with WPA), and for the most part it works. However, every 5-10 mins or so it will lose the connection and have to reconnect. It's able to successfully reconnect, so its not a showstopper for me but just wanted to see if others were having the same issue?
I'm certain its not my network for 2 reasons:
A) I've been streaming through my roku the whole time without issue on the same network.
B) I upgraded today from VEGAN GE RC1, and was not experiencing this issue when connecting to the same network since April on that ROM and used it successfully as recently as this afternoon.
So, I had 7.0.0 and I followed the directions from here: http://forum.xda-developers.com/showthread.php?t=865245 to install 7.1.0 and it's not working out. Did I miss something? I am currently stuck at "Powered by G-TABDEVS" screen. I am using loader 1.1 and I did grab the appropriate zip file.
Thanks in advance! Glad to see the project is on going!
Edit: 7.0.0 Seems to reinstall just fine. =/
dav_t said:
However, every 5-10 mins or so it will lose the connection and have to reconnect. It's able to successfully reconnect, so its not a showstopper for me but just wanted to see if others were having the same issue?
Click to expand...
Click to collapse
It may be due to the WLAN firmware blobs pershoot uses. He supplies newer Code Aurora Project supplied blobs with all his recent (since April '11) kernels which cause regular WiFi drops for me. The drops go away if I downgrade the firmware blobs to the Nvidia supplied ones that come with the VS (and NI Adam) stock firmware.
Get mine from here and report back. Use the CyanogenMod version which should work on all GB ROMs.
hey guys i'm in a bit of trouble lol feel free to call me an idiot. i know i am, i usually do more studying first and try to keep a backup of everything....but didnt this time.this feels alot more complicated than flashing an android phone!
so the gtab was given to me as a gift with regular froyo vegantab on it. i assumed everything was good and setup for me so i wiped data/cache and went to flash gingeredition with 1.1 bootloader zip. it loads up past the birds and just stays on the "powered by g-tabdevs" screen.
Next, i tried partitioning the sd card first and then flashing but still the same thing.
can anyone point me in the right direction?
Related
{
"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"
}
This thread is reserve for nightly build of Cyanogen Mod Rom for HTC Nexus One
You can report and discuss all issue you are having with nightly build here.
What are Nightly build ? : auto compil build from the CyanogenMod github, each time there are new corrections on it.
This version change each night, and aren't support officialy, if you find bugs/issues you can/must discuss here.
Warning: Not for new user, flash this build only if you know what you are doing !!!
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps from his roms,
after flashing rom don't forget to flash Google Addon package if you want it.
HBOOT-0.35.0017 (recommended): http://android.clients.google.com/packages/ota/passion/d6096cac5e9f.signed-hboot-0.35.0017.zip flash it like any other roms you already flash via recovery
Lastest version: CM7...
Download: http://mirror.teamdouche.net/?type=nightly&device=passion
MD5Sum: check the md5 under the files named associate with your build version before flashing it
Mirror: http://download.cyanogenmod.com/?type=nightly&device=passion
KANG: http://fitsnugly.euroskank.com/gigglebread/?id=passion
KANG: http://www.mediafire.com/temasek passion folder
Google Addon:
Choose the right version >
http://www.mediafire.com/temasek Unofficial GAPPS thanks to @Temasek
http://goo-inside.me/google-apps >Check the lastest package available on top
USEFUL
http://wiki.cyanogenmod.com/wiki/Barebones clean your rom to make space
CHANGELOG What's new in this version :
http://cm-nightlies.appspot.com/?device=passion
http://review.cyanogenmod.com/#q,status:merged,n,z
http://changelog.bbqdroid.org/#passion/cm7/next
If you have issue with this rom just WIPE ALL and try again.
Old version: 6.1.0...
Download: http://mirror.teamdouche.net/?type=nightly&device=passion
MD5Sum: check the md5 under the files named associate with your build version
Mirror: http://mirror1.kanged.net/nightly/passion/
Google Addon: HDPI-20101114
Mirror: http://goo-inside.me/google-apps/
Check the lastest HDPI package available on top
Radio Firmware: 4.0.6.00.12_7 (FROYO RADIO, REQUIRED!) or +
Download: http://android.chemlab.org/android/nexus/radio-4.06.00.12_7.img
MD5Sum: 3321c196d8ec1cf748fd20c3c4068520
Radios: http://forum.xda-developers.com/showthread.php?t=744605
Click to expand...
Click to collapse
Have a question or an issue? Try this before asking something silly:
inspired by gatsu_1981
Official Cyanogenmod forum - http://forum.cyanogenmod.com/topic/14446-nightlies-cm7-discussion-of-nightlies/
I noticed that the Gallery behaves weirdly when it encounters an empty album (from Picasa). It hides the empty albums but still occupy the space in the grid, sometimes it stops other albums from loading and makes it impossible to go into those albums.
All is ok after deleting the empty albums through Picasa Web Albums.
been running cm_passion-07122010-001202.zip for 10 hours, all wiped, no major problems here.
Nice Nice.. I'll be giving this a go..
EDIT:
second poster
With all of the nightly's and RC1, it takes FOREVER for widgets to load and for SU to grant root permissions to many if not all apps.
Very nice to see this thread as I have been running nightlys for several days.
The latest seems to be the best (122010), very fast, great carrier signal reception. So far I haven't had any fc's. Not a single issue so far. Good job on this one.
Ditto on the SU permissions problem.
Other than that, great battery life, speed and oh my how I missed all of the Cyan goodies when I defected to try another Froyo build.
Thank you Cyanogen and all of the other devs involved in this project!
can i just do a thrid [dammit im 7th] poster thingy ... gonna give it a try !!
Oh, I only did a wipe when I first went from 5.8 to the alpha 1, after that I haven't had to do a wipe.
I am having trouble running Metamorph with this version of CM. It is saying that I either do not have a SDCard in the phone or that there is not enough space. This message appears right after Metamorph is opened. Tried wiping it and even verified that I have over 60mb of space on the phone (metamorph says it needs at least 20mb). Can anyone verify this error? I know there are those who have installed blackbar morph successfully so any help with this matter would be greatly appreciated.
Netlocation has been a pain in my arse ever since Alpha 1, will post a log when I get back to my computer. It will only find my location over wifi, not network.
THATTON said:
With all of the nightly's and RC1, it takes FOREVER for widgets to load and for SU to grant root permissions to many if not all apps.
Click to expand...
Click to collapse
So glad to hear I am not the only one experiencing this.
Metamorph and Ninjamorph both work fine for me!, I have had that problem before though, i had to unistall and reinstall metamorph.
whoisthedrizzle said:
So glad to hear I am not the only one experiencing this.
Click to expand...
Click to collapse
You are definetely not the only one! Hopefully we will see a fix soon. I have faith in Teamdouche. They will get it done.
THATTON said:
With all of the nightly's and RC1, it takes FOREVER for widgets to load and for SU to grant root permissions to many if not all apps.
Click to expand...
Click to collapse
Ditto. Exchange also broke from alpha1... but I have ROM flashing OCD and I don't care!
Thx for creating this thread btw...
RixKliq said:
Ditto. Exchange also broke from alpha1... but I have ROM flashing OCD and I don't care!
Click to expand...
Click to collapse
Me: Hello, my name is Troy and I am an Android Addict.
Crowd: Hi Troy!
THATTON said:
Me: Hello, my name is Troy and I am an Android Addict.
Crowd: Hi Troy!
Click to expand...
Click to collapse
*insert Bob Saget line here*
Anyway, I filed a bug report when I was still on RC-1 about the SU set on boot things, and I starred a report about exchange.
I'm not getting root access anymore, even when manually opening apps (10min after boot). Rebooting doesn't solve it. Are more people having this issue, if so is there a fix for at least getting manual root access after losing it?
EDIT: nvm, got it after 15min of waiting.
damanrico said:
I'm not getting root access anymore, even when manually opening apps (10min after boot). Rebooting doesn't solve it. Are more people having this issue, if so is there a fix for at least getting manual root access after losing it?
EDIT: nvm, got it after 15min of waiting.
Click to expand...
Click to collapse
Yeah, it takes about 15 minutes for me as well.
Grimms said:
Nice Nice.. I'll be giving this a go..
EDIT:
second poster
Click to expand...
Click to collapse
Technically you were third, you could start your own topic and be first poster, although I fail to see why this is entertaining.
Most of the nightlies seem to be pretty stable, I'm running the current one and all seems to be ok. Cross-flashing from MCR breaks things horribly but that's not all that surprising. There's still a fair bit to be added in by the looks of things but most of it seems to be pretty stable. Just make sure to keep a couple of generations of Nandroid backups as one of the builds a couple of nights ago broke a few things fairly badly and I had to revert.
Добро пожаловать, друзья! Welcome, Friends! आपका स्वागत है, दोस्तों! Benvenuti, amici!
Bem-vindos, amigos! Ласкаво просимо, друзі! Bine ati venit, prieteni! 欢迎 朋友们
Vítejte, přátelé! chào đón, bạn bè! Willkommen, Freunde! Bienvenidos, amigos!
{
"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"
}
The latest CyanogenMod Nightly can be downloaded here or via ROMManager.
The new recovery in ROMManager (5.0.2.7) is not required, but is necessary to receive automatic updates.
Changelog
[I'm not going to provide my own changelog as all updates to CM7.2 are minor bugfixes only...]
Other necessary files: Google Apps (Also available in ROMManager)
night·ly /ˈnaɪtli/
adj.
Of or pertaining to the night, or to every night; happening or done by night, or every night.
A Fresh CyanogenMod ROM automatically built with the newest available code, usually compiled at night. Often contains many bugs.
Click to expand...
Click to collapse
This is the place to discuss the CyanogenMod nightlies. Feel free to talk about anything related to these ROMS, but to receive acknowledgement by a developer of any problems you find, the following conditions should be met:
Use the stock CyanogenMod kernel
Do not overclock
Use the default system apps (launcher etc.)
Do not use apps2sd or similar
Before posting a problem you should:
Check the posts below for a solution / fix
Read the last 10 pages of this thread for a post with a similar problem
Backup, reflash with a full wipe, check if the bug is still there
Wait 24 hours for the next nightly, the devs probably already know about it
If the problem still persists after the next nighlty appears and all the above steps have been followed, post your problem and we'll see if there is something we can do. Please include the following information:
Which Nightly you are running
Which Nightly the bug first appeared (if known)
*Confirm Stock Everything* (shows that you have read all the above)
Detailed steps to reproduce the bug (add a screenshot if it helps)
OLD BASEBAND?
If your phone uses the old baseband, you need to upgrade to the new baseband. This improves 3G signal and battery life. There are many guides on how to do this so just have a quick look around, or even watch a video on Youtube.
NO-APN PROBLEMS?
All APN problems related to 'funny SIMs' have been fixed, please thank werewolfo for generously donating an Italian funny SIM for me to test with!.
Major improvements include:
New baseband support
Better 3G Reception
.35 kernel support (only)
Offline charging
Quicker GPS lock
Smoother Accelerometers
Better 3G signal
Better battery life
CyanogenMod Updates
Mik is back?! Yeah!!!
Greets!
mDroidd said:
Mik is back?! Yeah!!!
Greets!
Click to expand...
Click to collapse
Really great news,I agree.
@adfad: Didn't know rmcc had a new whole p500 stuffs,thanks for the advices brother.
Aside from no data on T-Mobile UK, everything else seems to work fine.
People with data problems: Can you provide a radio logcat output please, the command you want is:
Code:
adb logcat -b radio
copy the output to http://pastebin.com/ and add the link here
Thanks!
digitalface said:
Aside from no data on T-Mobile UK, everything else seems to work fine.
Click to expand...
Click to collapse
One guy from dev thread suggested to flash baseband from latest official ROM for your country, may be that can help
He said:
"hey guys, try downloading the official gingerbread from vodafone in .kdz, extract the baseband from that rom and use it in your rom. If you don't know how, PM me."
Here is the link:
http://forum.xda-developers.com/showthread.php?p=21370547
@adfad
What do you think about that bug:Call settings/additional settings doesn't work. An error "network or Sim card error" occurs. This works in official roms and doesn't work in mik's 6.5.8 too.
lerkin said:
One guy from dev thread suggested to flash baseband from latest official ROM for your country, may be that can help
He said:
"hey guys, try downloading the official gingerbread from vodafone in .kdz, extract the baseband from that rom and use it in your rom. If you don't know how, PM me."
Here is the link:
http://forum.xda-developers.com/showthread.php?p=21370547
Sent from my LG-P500
Click to expand...
Click to collapse
It shouldn't make a difference, especially since it's been reported roms based on official LG gingerbread work with the same baseband
lerkin said:
What do you think about that bug:Call settings/additional settings doesn't work. An error "network or Sim card error" occurs. This works in official roms and doesn't work in mik's 6.5.8 too.
Click to expand...
Click to collapse
I've noted it, but the main bug should be to get this network problem sorted out. Just need to get some logcat readings as described above
Logcat
Logcat with WiFi enabled:
pastebin.com/735b5cz1
Logcat with GSM enabled:
pastebin.com/A1V0hZ2P
Sorry, I can't post links because I have not enough posts yet.
btw: great rom, thx for your work
Edit: Nightly 1, nothing changed
OS:Nightly full-1
*Camera... oops! AM I wrong or my phone or gallery started to take photos or and recording movies by 90 degrees counter-clockwise? That's strange behavior...
Too many resolutions in photo camera... maybe i am wrong but i never seen 1080p and 720p types in CMcamera
Here is my logcat (E-Plus Germany) calls are working, mobile data doesn't work.
http://pastebin.com/EvWRuxsz
homepage32 said:
Logcat with GSM enabled:
pastebin.com/A1V0hZ2P
Click to expand...
Click to collapse
Kaerper said:
Herese is my logcat (E-Plus Germany) calls are working, mobile data doesn't work.
http://pastebin.com/EvWRuxsz
Click to expand...
Click to collapse
Thanks, now can you do provide me with a full logcat from boot please. Switch it off, then back on and wait until the lock screen comes on and the screen times out and switches off.
(not the command from above, just a regular adb logcat)
Hope this is what you want...
http://pastebin.com/LAGXwC88
lerkin said:
What do you think about that bug:Call settings/additional settings doesn't work. An error "network or Sim card error" occurs. This works in official roms and doesn't work in mik's 6.5.8 too.
Click to expand...
Click to collapse
The problem is a CyanogenMod problem. Someone has already submitted some patches recently, I've tested them and they work fine so they should be merged very soon.
I encounter a pretty annoying bug with outgoing/incoming calls. I cannot hang up after the phone after the conversation. I get a a blackscreen. When the other person at the other end hangs up the sound comes on to say call has been disconnected. After this, you cannot use your phone. pushing and holding the power key only makes your buttons (on the phone) flash. You have to remove battery and reboot in order to fix the problem.
Nightly: #1.
Kaerper said:
Hope this is what you want...
http://pastebin.com/LAGXwC88
Click to expand...
Click to collapse
Hmm nothing funny there either. I'll need to see the logcat of the radio again but from boot (1st command again). It scrolls pretty quick sometimes so try to get it all from the very beginning.
edit - this might be easier:
Code:
adb logcat -b radio > logcat.txt
switch the phone off, run the command BEFORE you switch the phone on (it'll say waiting for device) then switch the phone on and wait until you see the lock screen. you won't see anything on the screen, it saves it all to the logcat.txt file.
press ctrl + C to quit adb and paste the content of the file
ScripterJR said:
I encounter a pretty annoying bug with outgoing/incoming calls. I cannot hang up after the phone after the conversation. I get a a blackscreen. When the other person at the other end hangs up the sound comes on to say call has been disconnected. After this, you cannot use your phone. pushing and holding the power key only makes your buttons (on the phone) flash. You have to remove battery and reboot in order to fix the problem.
Nightly: #1.
Click to expand...
Click to collapse
The proximity sensor driver needed updating in the kernel, it's already fixed and will be in Nightly #2. However there is a fix, plug the phone in to charge and it comes back to life!
Is this going to stay on new baseband? I just don't see the need in upgrading baseband if mobile data doesn't work
Sent from my LG-P500 using xda premium
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
{
"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"
}
Click link here>> Droid DNA [OFFICIAL] LiquidSmooth ROM page <<Click link here
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
Please keep discussion focused, on the topic described in the OP
~Reserved~
1 more just in case
ROM's great, have a couple questions
1. I get an odd notification for emails that won't stop until I drag down status bar. I'm sure it's something I activated but can't, for the life me, find
2. Is there updated firmware/radios to use with KK? My battery life has gone in the toilet when mobile data on. Shut it off and battery lasts forever. I know data uses more battery but only lasts half a day with data on/ minimal use.
Sent from my HTC6435LVW using xda app-developers app
stock messaging app
I installed the latest version of LS 3.0 and my stock messaging app refuses to open. I tried posting on the Google+ site for it but no answer. And I am not allowed to post on the ROM thread so I figured I'd try here. I am just wondering if its broken or is it something I can fix. I tried installing a couple messaging apps but they won't open either. And I hate hangouts. Love the rest of the ROM but no messaging app is a deal breaker for me
Keyboard Landscape mode error??
So whenever i turn my phone to the side (landscape) the keyboard is either not there or just the top of it appears, as if its "under the phone". I can deal with typing in portrait mode, but i would like to eventually fond a fix for this??
Liquidsmooth - unable to change alarm or ring tone
When changing the sound profile to a new sound the alarm or ring tone, I cannot select a different sound. When the option to change the path shows up, the option for changing to /system/media/audio/alarms or /system/media/ui /system/media/audio/ringtones is not possible.
LiquidSmooth Floating Window issue with Chrome Beta
Any idea why my chrome beta will only open in floating mode unless I open it from recents? Tried clearing cache/data and reinstalling it to no avail.
5.0.2 Droid DNA
OK so first off let me start by saying I love having lollipop on my Droid DNA!! Now with that being said I have a question, I love having double tap to wake but is there a way to either disable it all together (last ditch effort), or preferably just have the bottom three buttons not wake the phone? For some reason when I push the back of my phone it thinks I hit the home button and wakes the screen making me have a horrible battery life. Any insight would be much appreciated!
BuddyHiggins said:
OK so first off let me start by saying I love having lollipop on my Droid DNA!! Now with that being said I have a question, I love having double tap to wake but is there a way to either disable it all together (last ditch effort), or preferably just have the bottom three buttons not wake the phone? For some reason when I push the back of my phone it thinks I hit the home button and wakes the screen making me have a horrible battery life. Any insight would be much appreciated!
Click to expand...
Click to collapse
Disregard that! It was a Kernel issue!! Thanks anyway!
Bluetooth Issue
I am also running into Bluetooth issues with this ROM too. Certainly a bit frustrating as that's the one thing I've been having a major problem with, and is preventing me from using it as my daily driver.
Every time I toggle Bluetooth from 'On' to 'Off', I receive an error message stating that Bluetooth Share has stopped (see attached screenshot).
As soon as this message has popped up once, I can no longer stream audio via Bluetooth whatsoever, even after attempting to unpair and re-pair the device and/or rebooting my phone. The audio will either play in tiny little flits and spurts for a second or two and drop off completely, or will play for a split second initially and then drop off.
I encounter no Bluetooth issues whatsoever, with the exact same hardware, using one of Santod's other Lollipop dlx ROMs however ([ROM][5.0.1] Google Play Edition | Lollipop | v1.02 [12-06-14]).
Thoughts?
Anyone? Bueller?
OblivionOcean said:
I am also running into Bluetooth issues with this ROM too. Certainly a bit frustrating as that's the one thing I've been having a major problem with, and is preventing me from using it as my daily driver.
Every time I toggle Bluetooth from 'On' to 'Off', I receive an error message stating that Bluetooth Share has stopped (see attached screenshot).
As soon as this message has popped up once, I can no longer stream audio via Bluetooth whatsoever, even after attempting to unpair and re-pair the device and/or rebooting my phone. The audio will either play in tiny little flits and spurts for a second or two and drop off completely, or will play for a split second initially and then drop off.
I encounter no Bluetooth issues whatsoever, with the exact same hardware, using one of Santod's other Lollipop dlx ROMs however ([ROM][5.0.1] Google Play Edition | Lollipop | v1.02 [12-06-14]).
Thoughts?
Click to expand...
Click to collapse
*BUMP*
Anyone encounter bluetooth issues such as this that they were able to fix? I'm dying to get this addressed and use this otherwise kickass ROM as my daily driver!
Failed to Install with TWRP/CWM Recovery
I'm having a bit of an issue while trying to install this ROM to my HTC DNA. I keep trying to install LS-LP-v4.0-2015-01-12-liquid_dlx.zip, but whenever I do, it gives me this error:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E: Error in /data/media/0/Lollipop/LS-LP-v4.0-2015-01-12-liquid_dlx.zip
(Status 7)
Installation aborted.
Any idea what's going on? I've tried doing this on TWRP 2.7.0.0 and ClockWorkMod Recovery v6.0.4.5, but both give me the same error. I've run a factory reset each time before installing as well. Transitioning over from from ViperDNA Sense 6.
EDIT: It changed to this error log:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file name or directory
E: Error in /data/media/0/Lollipop/LS-LP-v4.0-2015-01-12-liquid-dlx.zip
(Status 0)
Installation aborted.
My phone is currently sitting without a ROM installed, so this could become a bit more of a problem. Yes, I created a backup, but it's not being recognized by either Recovery tool.
bringing support to HTC butterfly
nice work, i have been a fan of liquid smooth roms when i had Motorola razr, i wonder if you can bring the support to the international version of droid DNA which is htc butterfly, (x920d) i would appreciate it a lot
I too am having the same issue. I haven't found or heard of a fix. There has been talk on the Official CM12 thread that BT has been fixed with the latest nightly. Im just hoping that the next build of this ROM incorporates the fix.
Q&A for [ROM][EXP] AOSP Lollipop 5.0 for Evo 3D - November 12
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][EXP] AOSP Lollipop 5.0 for Evo 3D - November 12. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Good job! It's looked very sexy :fingers-crossed::fingers-crossed::fingers-crossed:
Awesome!!!
Gapps
Hi, I got a problem with gapps. I tried 4.4 gapps and cyanogenmod 12 gapps. Everytime I boot there is an error saying process *.wizard has failed. Basically all google services fail. So what gapps should I use. Thank you Hahaburger for this rom which works fine without gapps.
flashed
Hi, i flashed this rom earlier today and now I am stuck. when the phone turns on it tells me in a different language then english roughly translated "sorry but wizard application for settings has quit" and when i click OK the same message pops up. it just repeats. when I shut off and enter bootloader using the power and volume down buttons and try to go to recovery to restore the phone just shuts off which i can not turn back on without taking out the battery. HELP ME i am stuck. what can i do to fix this or restore back to a previous build
i did a full wipe, flashed this rom, then supersu.
after that i manually installed some apps via adb.
so far my experience has been very good considering this early stage of development!
its running smooth, no major problems so far, even the flashlight is working (although System-UI fcs when i activate it)
after a full day of light usage (no calls, no sms) only using wifi for chat/mail/browser and installing some apps, i still have over 80% left.
but when i try to call someone i just get an error saying something like "call not connected."
Here is a logcat: pastebin com /ZrbZTGtL
i think the error happens around these lines:
80. Telephony( 752): TelephonyConnectionService: Could not get subId from account: E
115. PhoneInterfaceManager( 752): [PhoneIntfMgr] getIccId: ICC ID is null or empty.
+ some more like the last one
---------- Post added at 07:53 PM ---------- Previous post was at 07:31 PM ----------
here is a logcat of the flashlight crashing System-UI
pastebin com /tsusu00p
i think it has to do with the camera not working yet but here are some errors:
D/QualcommCameraHardware3D( 189): getBuffersAndStartPreview: setPreviewWindow(320 x 240), iTotalBufferCount 5, mIs3DModeOn: 0
E/ ( 133): unrecognized pixel format: 0xf0
E/ ( 133): Format 240
W/GraphicBufferAllocator( 133): alloc(115200, 76800, 240, 00000100, ...) failed -22 (Invalid argument)
E/ ( 133): GraphicBufferAlloc::createGraphicBuffer(w=115200, h=76800) failed (Invalid argument), handle=0x0
E/BufferQueueProducer( 1281): [unnamed-1281-1] dequeueBuffer: createGraphicBuffer failed
E/QualcommCameraHardware3D( 189): getBuffersAndStartPreview: dequeueBuffer failed for preview buffer. Error = FFFFFFEA
Click to expand...
Click to collapse
the funny thing is i can hear the camera making shutter noises, so it's at least doing something with the camera
echs said:
i did a full wipe, flashed this rom, then supersu.
after that i manually installed some apps via adb.
so far my experience has been very good considering this early stage of development!
its running smooth, no major problems so far, even the flashlight is working (although System-UI fcs when i activate it)
after a full day of light usage (no calls, no sms) only using wifi for chat/mail/browser and installing some apps, i still have over 80% left.
but when i try to call someone i just get an error saying something like "call not connected."
Here is a logcat: pastebin com /ZrbZTGtL
i think the error happens around these lines:
80. Telephony( 752): TelephonyConnectionService: Could not get subId from account: E
115. PhoneInterfaceManager( 752): [PhoneIntfMgr] getIccId: ICC ID is null or empty.
+ some more like the last one
---------- Post added at 07:53 PM ---------- Previous post was at 07:31 PM ----------
here is a logcat of the flashlight crashing System-UI
pastebin com /tsusu00p
i think it has to do with the camera not working yet but here are some errors:
the funny thing is i can hear the camera making shutter noises, so it's at least doing something with the camera
Click to expand...
Click to collapse
@HaHaBuRGeR
echs said:
80. Telephony( 752): TelephonyConnectionService: Could not get subId from account: E
115. PhoneInterfaceManager( 752): [PhoneIntfMgr] getIccId: ICC ID is null or empty.
+ some more like the last one
Click to expand...
Click to collapse
Thanks for detailed explanation and logcats . I'm aware of this erros.
I'm trying to debug rild to find problems. Also for camera it seems codec error.
I'll look at that too after mobile data. And I can make calls I don't really know why you can't.
Are you using usim? If you would like to test more please send me a PM.
@HaHaBuRGeR:
i don't know how to find out if i have an USIM. according to some older posts regarding my provider all newer sims should be USIM.
i found some code examples but in most cases CDMA was detected as a USIM and GPRS as SIM.
on the sim card i have the letters UJ, the U should be for a USIM card but i'm not sure.. i'd guess its an USIM.
sms are working fine (sending and receiving).
i could receive calls and they were working fine.
but i still cannot make outgoing calls. USSD codes also aren't working.
btw: i got almost 48hours of uptime with no major errors, it's gonna be a fine rom!
still waiting for data, atm thats more important to me.
oh and i cannot send PMs until i have 10 posts...
Google PlayStore problem
I really like your ROM, have used it for week...
I have the last release - working (call, sms, headphones) ok and fast, but I'm not able to install apss from store (I got unknown error code 972 ).
I used the GApps from here: https://s.basketbuild.com/gapps . Which GApps are recommended for you ROM?
cajda77 said:
I really like your ROM, have used it for week...
I have the last release - working (call, sms, headphones) ok and fast, but I'm not able to install apss from store (I got unknown error code 972 ).
I used the GApps from here: https://s.basketbuild.com/gapps . Which GApps are recommended for you ROM?
Click to expand...
Click to collapse
Weird, I'm using same GApps for testing. Have you wiped your data partition before installing the ROM?
HaHaBuRGeR said:
Weird, I'm using same GApps for testing. Have you wiped your data partition before installing the ROM?
Click to expand...
Click to collapse
Yes, I'did.
I'll try tommorow again (the whole flash process) just to be sure. I don't know how to provide you more info...I'll try to look in syslog.
cajda77 said:
Yes, I'did.
I'll try tommorow again (the whole flash process) just to be sure. I don't know how to provide you more info...I'll try to look in syslog.
Click to expand...
Click to collapse
You can install and use adb to give me logs about errors. Here is a tutorial about how to use it http://forum.xda-developers.com/showthread.php?t=1726238
Unfortunate that this a GSM ROM because I'm on CDMA so I could possibly help out
Sent from my Evo 3D CDMA
HaHaBuRGeR said:
You can install and use adb to give me logs about errors. Here is a tutorial about how to use it http://forum.xda-developers.com/showthread.php?t=1726238
Click to expand...
Click to collapse
Probably the problem was that I used old recovery for flashing (TWRT, CWM), I got some errors. Today I have used the PhilZ Touch from here: http://forum.xda-developers.com/showthread.php?t=2764698 and GooglePlay installing apps seems to be working.
Thanks
Interesting! Seeing I still use my HTC Evo 3D as my daily driver, I'm going to try to work on a L version for CDMA and probably start here.
This would be my first try doing anything ROM related in terms of development, so it'll be interesting for me. I wish you luck in getting this thing into a daily driver on this old device . At least we are not forgotten!
No_file contexts
No_file contexts everytime I try to install it? On latest build It just stays on installing update.. adn nothing happens latest CWM recovery I really want to istall it
When I try to install the SELinux-disabled kernel I get this message in the photo. Is it normal? Flashing finishes OK, but when I reboot I still have no su access. I must mention that I have installed this ROM in dual-boot, so recovery sees my primary ROM environment which is ICS.
{
"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 Oppo Find 7a X9007 with rare/no GSM/3G reception
ergün
ergün kardeş bana face adresini versene sormam gereken şeyler varda.
dreccon said:
When I try to install the SELinux-disabled kernel I get this message in the photo. Is it normal? Flashing finishes OK, but when I reboot I still have no su access. I must mention that I have installed this ROM in dual-boot, so recovery sees my primary ROM environment which is ICS.
Sent from my Oppo Find 7a X9007 with rare/no GSM/3G reception
Click to expand...
Click to collapse
I have no idea for dual-boot but we don't need SELinux disabled kernel anymore for using su command. You can just flash superSU's latest version, it works well.
CLOSED
reserved
reversed
xD
moonbutt74 said:
reversed
xD
Click to expand...
Click to collapse
Thanks
CM12
Thought you said you was not going to do anything to do with cm12 xD
denniso08 said:
Thought you said you was not going to do anything to do with cm12 xD
Click to expand...
Click to collapse
I umm....RUN AWAY !!!
okay, okay i fibbed a little, you got me... :laugh:
@sub77 's build is running quite nicely !
We need a theme package, seperate from having to goto google play.
At least for the browser, it's so [BLEEPING] ugly.
m
device ue?
It wont let me flash his rom due to it being a ue device, why is that?
Please help me, i want to Lollipop :3
denniso08 said:
It wont let me flash his rom due to it being a ue device, why is that?
Click to expand...
Click to collapse
D,
hi,
because this kernel package is for the milletwifiue sm-t330nu
to address the shortcomings of the kerne in sub77's cm12 rom build for
the sm-t330nu,
Additionally, i make no adjustments for twrp, i use my own recovery build [Philz]
also, i will not remove the updater-script device assert. That is for the individual user to do.
Now that being said, remove the assert from the updater script and give it a try, just , as always, make
a backup first.
This is not, as per OP, not for the sm-t530/nu/31 etc.
m
Notacoder.com
I have no clue how I would do that xD
neitheramibutitsnothathard.gov/NSA/nicepr0nfolderyagotthereson
denniso08 said:
I have no clue how I would do that xD
Click to expand...
Click to collapse
It's a zip file. Open it on your PC with winrar or 7zip, go to META-INF/com/google/android/ and extract updater-script. Open it with notepad++ and edit out the first few lines, it should be pretty self-evident which lines comprise the assert. Delete those. Put the edited updater-script right back in the same folder in that zip and flash it. Also doable on your tablet, but it's a tad more cumbersome doing it that way, always easier to do on a PC.
moonbutt74 said:
D,
hi,
because this kernel package is for the milletwifiue sm-t330nu
to address the shortcomings of the kerne in sub77's cm12 rom build for
the sm-t330nu,
Additionally, i make no adjustments for twrp, i use my own recovery build [Philz]
also, i will not remove the updater-script device assert. That is for the individual user to do.
Now that being said, remove the assert from the updater script and give it a try, just , as always, make
a backup first.
This is not, as per OP, not for the sm-t530/nu/31 etc.
m
Click to expand...
Click to collapse
Ummm, but.... The galaxy tab 4 sm-t330nu Is the milletwifiue..... If it's the same as the cm 12.1 ROM it won't flash because the milletwifi and the milletwifixx are the only two models included in the asserts, which is totally backwards since it explicitly states it's for the milletwifiue. IMO
Edit:
Nope it should flash on his device, the kernel package does include the milletwifiue in its assert
Edit 2:
Totally missed that the original question was about the ROM, not the kernel. If you look in the ROM thread this was covered yesterday
Exile1975 said:
Ummm, but.... The galaxy tab 4 sm-t330nu Is the milletwifiue..... If it's the same as the cm 12.1 ROM it won't flash because the milletwifi and the milletwifixx are the only two models included in the asserts, which is totally backwards since it explicitly states it's for the milletwifiue. IMO
Click to expand...
Click to collapse
Yes, however, I am only answering questions about this kernel package. Questions about the rom should be asked on sub77 's thread.
This is the assert for MY updater script
Code:
assert(getprop("ro.product.device") == "milletwifi" ||
getprop("ro.build.product") == "milletwifi" ||
getprop("ro.product.device") == "milletwifiue" ||
getprop("ro.build.product") == "milletwifiue" ||
getprop("ro.product.device") == "milletwifixx" ||
getprop("ro.build.product") == "milletwifixx" ||
abort("This package is for device: milletwifi,milletwifiue,milletwifixx; this device is " + getprop("ro.product.device") + "."););
This is the assert for sub77's updater script
Code:
assert(getthread("ro.sub77's-rom.thread") == " http://forum.xda-developers.com/tab-4/development/rom-cyanogenmod-12-1-t3097152 " ||
abort("This is the wrong thread for your question: http://forum.xda-developers.com/tab-4/development/rom-cyanogenmod-12-1-t3097152; this thread is " + getprop("ro.moonbutt74's-kernel.thread") + "."););
xD
okay seriously though change or update your recovery, there's nothing backwards or conspiratorial about screwy device asserts, it happens.
or remove the assert.
And when all else fails see this video before proceeding https://www.youtube.com/watch?v=JmvCpR45LKA
{
"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"
}
m
moonbutt74 said:
Yes, however, I am only answering questions about this kernel package. Questions about the rom should be asked on sub77 's thread.
m
Click to expand...
Click to collapse
Guess we both misread the original question then since it was about the ROM.
But hey, wanted to say thanks for the kernel. Working beautifully.
Exile1975 said:
Guess we both misread the original question then since it was about the ROM.
But hey, wanted to say thanks for the kernel. Working beautifully.
Click to expand...
Click to collapse
E,
hi, are you experiencing the issue with power off charging ?
I think i have it pegged to lpm
after looking through the stock boot.img the lpm service is there
calling to /system/bin/lpm
which relies on [proprietary]
libmaet.so
libsxqk_skia.so
if you would, make a backup of your current rom and reflash sub77's release without flashing my kernel.
after you done getting through setup, make sure the tab is not connected to usb or power,
then shut off your device and plug it in. i am trying to determine if it's in the kernel or ramdisk config/setting is missing.
thanks.
m
to users of my cm11 build, also please let me know if this issue is occuring since it is the same kernel.
moonbutt74 said:
E,
hi, are you experiencing the issue with power off charging ?
I think i have it pegged to lpm
after looking through the stock boot.img the lpm service is there
calling to /system/bin/lpm
which relies on [proprietary]
libmaet.so
libsxqk_skia.so
if you would, make a backup of your current rom and reflash sub77's release without flashing my kernel.
after you done getting through setup, make sure the tab is not connected to usb or power,
then shut off your device and plug it in. i am trying to determine if it's in the kernel or ramdisk config/setting is missing.
thanks.
m
to users of my cm11 build, also please let me know if this issue is occuring since it is the same kernel.
Click to expand...
Click to collapse
M,
I did a factory reset and restored a backup from stock. Did anther factory reset and installed the CM package. First boot was fine, restarted, shut down, plugged in, and it charges while remaining shut off. With your kernel I have what is described elsewhere. When the tablet is turned off and I plug in, the charging icon shows briefly, then the tablet boots. Hope this helps.
E,
hi, thanks, i am reworking my source.
m
[kernel] cm12 sm-t330nu - UPDATED
okay,
after a couple of tests the issue seemed to be with the ramdisk sepolicy/init.
Power off charging issue should be resolved as per my testing
cm12-kernel-carmilla-linaro-milletwifiue-V2.zip
https://www.androidfilehost.com/?fid=23991606952596384
m
moonbutt74 said:
okay,
after a couple of tests the issue seemed to be with the ramdisk sepolicy/init.
Power off charging issue should be resolved as per my testing
cm12-kernel-carmilla-linaro-milletwifiue-V2.zip
https://www.androidfilehost.com/?fid=23991606952596384
m
Click to expand...
Click to collapse
M,
I can confirm it charges while off now. As far as stability it seems rock solid, but I'll let you know if I notice anything. Thanks again for all your hard work and super fast response to solve this. If there's ever anything I can do for you just let me know.
Exile1975 said:
M,
I can confirm it charges while off now. As far as stability it seems rock solid, but I'll let you know if I notice anything. Thanks again for all your hard work and super fast response to solve this. If there's ever anything I can do for you just let me know.
Click to expand...
Click to collapse
E,
hi, thank you for your reply, by all means update me, it's how i learn.
Keep your posts in the right threads and we're good, no worries. :good:
m
moonbutt74 said:
E,
hi, thank you for your reply, by all means update me, it's how i learn.
Keep your posts in the right threads and we're good, no worries. :good:
m
Click to expand...
Click to collapse
Mine charges now to while its turned off. Thanks