Hi,
I'm currently on cm-11-20131207-NIGHTLY-mako.zip and wanted to dirty-flash omni-4.4.1-20131208-mako-NIGHTLY.zip.
But when booting Android I get lots of messages like "android.database.sqlite.SQLiteException: Can't downgrade database from version 589832 to 524296" - among others for dialer, mms, settings storage - and Android reboots.
I understand why these messages appear and why Android won't start properly. I also know that the only real issue here is the DB versions, not some compatibility problem.
My actual question/request is: Are there any plans to bump the db versions to be compatible with CM11 to enable easy transition from CM to Omni? If not, maybe that could be put on the wishlist?
Regards
XlAfbk said:
Hi,
I'm currently on cm-11-20131207-NIGHTLY-mako.zip and wanted to dirty-flash omni-4.4.1-20131208-mako-NIGHTLY.zip.
But when booting Android I get lots of messages like "android.database.sqlite.SQLiteException: Can't downgrade database from version 589832 to 524296" - among others for dialer, mms, settings storage - and Android reboots.
I understand why these messages appear and why Android won't start properly. I also know that the only real issue here is the DB versions, not some compatibility problem.
My actual question/request is: Are there any plans to bump the db versions to be compatible with CM11 to enable easy transition from CM to Omni? If not, maybe that could be put on the wishlist?
Regards
Click to expand...
Click to collapse
No. Dirty cross-flashing between firmwares is NEVER supported. Only upgrades from the same project. (In theory, you should be able to safely transition from 4.3 Omni to 4.4 Omni unless we screwed up. I know I successfully took my Tablet Z from 4.3 to 4.4 without issues other than some Google Calendar derps)
XlAfbk said:
Hi,
I'm currently on cm-11-20131207-NIGHTLY-mako.zip and wanted to dirty-flash omni-4.4.1-20131208-mako-NIGHTLY.zip.
But when booting Android I get lots of messages like "android.database.sqlite.SQLiteException: Can't downgrade database from version 589832 to 524296" - among others for dialer, mms, settings storage - and Android reboots.
I understand why these messages appear and why Android won't start properly. I also know that the only real issue here is the DB versions, not some compatibility problem.
My actual question/request is: Are there any plans to bump the db versions to be compatible with CM11 to enable easy transition from CM to Omni? If not, maybe that could be put on the wishlist?
Regards
Click to expand...
Click to collapse
Actually, it is a compatibility problem. The version of the database is really the version of the schema, not the version of the database program. The schema basically describes the tables in the DB and the columns in those tables. Different ROMs may have different tables due to different settings and features, and they're not compatible. In some cases where one ROM is literally a fork of the other it may work but generally this is not the case.
iofthestorm said:
Actually, it is a compatibility problem. The version of the database is really the version of the schema, not the version of the database program.
Click to expand...
Click to collapse
I understand that, should maybe have phrased my question differently: Any plans to update the db schemas to be in line with CMs?
As stated I'm well aware of possible compatibility problems and am willing to fix/clear data for individual apps, but for testing a new ROM i'm not really willing to do a factory reset just because ~5 dbs may be incompatible and their apps may FC.
Entropy512 said:
No. Dirty cross-flashing between firmwares is NEVER supported. Only upgrades from the same project. (In theory, you should be able to safely transition from 4.3 Omni to 4.4 Omni unless we screwed up. I know I successfully took my Tablet Z from 4.3 to 4.4 without issues other than some Google Calendar derps)
Click to expand...
Click to collapse
This does work in practice, as I did that w/ my "Tempest" flavor of Omni. 4.3-4.4-4.4.1 without any factory resets.
But I agree with Entropy. Never dirty flash. I keep an up-to-date Titanium Backup with all the user apps backed up, personally, and Accounts info/WiFi Networks/BT Pairings. Then, when I flash a new ROM, I have TiBa in a flashable zip and GApps, and I'm ready to go in just a few minutes after a factory reset.
XlAfbk said:
I understand that, should maybe have phrased my question differently: Any plans to update the db schemas to be in line with CMs?
As stated I'm well aware of possible compatibility problems and am willing to fix/clear data for individual apps, but for testing a new ROM i'm not really willing to do a factory reset just because ~5 dbs may be incompatible and their apps may FC.
Click to expand...
Click to collapse
No, the only way to achieve this is to be an exact clone of CM - which we are not.
XlAfbk said:
I understand that, should maybe have phrased my question differently: Any plans to update the db schemas to be in line with CMs?
As stated I'm well aware of possible compatibility problems and am willing to fix/clear data for individual apps, but for testing a new ROM i'm not really willing to do a factory reset just because ~5 dbs may be incompatible and their apps may FC.
Click to expand...
Click to collapse
Describing what you are asking in a simpler to understand analogy:
"I'm moving from New York to California, can I have the exact same interior layout and just drag and drop everything into the same location in my new home?"
You already know the answer, but in technical sense you are asking the omni team to plan and architect their interior design to the same as CM. Architects in New York and California will have completely different visions, based on the goals of the community they support.
It should not be standardized IMO.
Re install the stock filmware
Sent from my GT-I9070 using xda app-developers app
Related
I successfully installed a rom called USBWOOT.zip (thanks to all the hard work of the developers here, thanks so much guys!) however after doing a little more research I saw someone say the cm9 rom was better (latest one is here I think: http://forum.xda-developers.com/showthread.php?t=1411895&page=210)
I've also seen a MIUI version.
Is there some kind of chart showing the pros and cons of each?
I also have some other noob questions:
Can I flash a new rom (like an updated version, or a different rom?) without losing all my settings, accounts, apps, etc? Or do I have to do a factory reset every time and start over?
Why I ask is I flashed the USBWOOT.zip originally, but it looks like the latest version (in that post I linked to) cm9-02-19.zip has some updates that sound really nice (especially the 200ms to 80ms wait time on screen change)
Since I flashed USBWOOT.zip originally do I need to do a factory reset first or can I just flash cm9-02-19.zip? If I have to do a factory reset will I lose all the accounts, apps, etc?
Thanks for all the help!
That cm9-02-1* roms are follow ups to USBWOOT.zip, they are build from the same source, it just uses a different name coding. Usually all build in that thread are very similar, even if they are build from different people and are named differently since our development is open source.
I would try it first without a total wipe, if you have any unkown problems then do a total wipe. (But a total wipe from time to time isn't a bad thing, since these days many things may change between versions)
MIUI uses a different launcher & other stuff.
I just updated to the latest build of CM9 as well. So far so good. Here is the link too. http://www.mediafire.com/?tnoxgzcgop46odm
Sent from my Amazon Kindle Fire using xda premium
zacpac2020 said:
Install the ROM from this post. It's the most mature. CM9, by the way. http://www.mediafire.com/?tnoxgzcgop46odm
Thank me if I've helped PLEASE!!!!
Click to expand...
Click to collapse
Can you link us to the thread of the developer who compiled this Rom? Someone may want to read the discussion before blindly flashing an unknown zip file.
if its the same rom but just an update, you should get away with just flashing it on top and wiping dalvik cache. as always BACKUP FIRST and then resore and wipe if its not working like it should.
dont go with MIUI yet as its had way less work done and it doesnt even have USB ready.
It Worked
Thanks guys! I was able to flash the latest version without having to do any wipe or factory reset.
I am loving my new and improved Kindle Fire.
Kapurnicus said:
Can you link us to the thread of the developer who compiled this Rom? Someone may want to read the discussion before blindly flashing an unknown zip file.
Click to expand...
Click to collapse
looks like it comes from this thread: http://forum.xda-developers.com/showthread.php?t=1411895
Posting here as I'm a noob, and consequently can't post to the P.A page directly.
Since this 2.12 update i've been having wifi issues, like from where i am positioned normally I get 1 bar, but its a steady one bar, now i'm often finding i have no internet connection in the same places as i would before.
I did do a dirty flash, so that is most probably where all my problems are arising from, but i'm still really new to this, and any step i take, i worry and fret over.
had some tablet ui bugs after running games, along with all applications running twice when i open recent apps. I don't know where why or when this recent apps double bug occurs, but i've come across it a few times. I believe the tablet ui bug may be related to when i set bobclock (widget) to force, adjusted the size on restart, but then would encounter the icons dropped off bottom of screen, and everything just out of place, like its reverted to old ui.
oh another issue, which has been mentioned many times before, is inability to use google play store, i've fiddled with all the different dpi settings and size, nothing seems to work.
a clean wipe would include
backing up apps/data/p.a sys pref(?)
wiping
cleaning cache's
flashing the same 2.12 p.a zip i dirty flashed before
caches again? or gapps
any dumbing down would be greatly appreciated
Just to say version 2.13 is out. You might want to try updating in the first instance...
Sent from my Nexus 7 using xda premium
StrangerWeather said:
Just to say version 2.13 is out. You might want to try updating in the first instance...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
oh.. so there is. well i guess i can just skip over 2.12
if doing a dirty flash, when reinstalling gapps, do i have to have deleted them prior to this? or will it just replace/update the old files?
No, you don't need to. Just wipe both caches and install the new version and gapps.
Sent from my Nexus 7 using xda premium
StrangerWeather said:
Just to say version 2.13 is out. You might want to try updating in the first instance...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
oh cool.... is there a change log? or the question is, where would i see the change log?
Updating ... nevermind, i got what i need
we got any paranoid android avid fans here? running on the nux 7, ofc.
and by avid fan i mean, quite knowledgable, maybe able to help with some issues that may arise, being under 10 post count, there very little i can do it actually get any relevant help, ie to p.a
there is just so much information here, and being new to the android scene, consequently rooting roms and such as well. quite a bit is over my head but i'm doing my best! or well trying
`etcH said:
we got any paranoid android avid fans here? running on the nux 7, ofc.
and by avid fan i mean, quite knowledgable, maybe able to help with some issues that may arise, being under 10 post count, there very little i can do it actually get any relevant help, ie to p.a
there is just so much information here, and being new to the android scene, consequently rooting roms and such as well. quite a bit is over my head but i'm doing my best! or well trying
Click to expand...
Click to collapse
What sort of help are you looking for? I can try to answer any questions you might have, but your best bet is to search the paranoid android forum in the 'Original Development' section.
Sent from my Paranoid Nexus 7
RockNrolling said:
What sort of help are you looking for? I can try to answer any questions you might have, but your best bet is to search the paranoid android forum in the 'Original Development' section.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
i shall head over there and have a browse. will report back, need to get myself to 10posts so i can share bugs and such that i've encountered
Wouldn't Kernel be more specifically tied to WiFi issues? I don't know what PA does to the kernel they include, but if your up to it, you could try another kernel, like franco.Kernel
Oh. Yes. i've been on that page and have trolled through a few hundred pages.
I think I just need to become a bit more familiar with everything in regards to roms flashing and such, its not difficult but i fear i'm sure to do something in the wrong order,
yes i've read guides before you point me there.
gosh this 5 min wait timer for new people is getting on my nerves i didn't think i'd be wanting to reply so fast, but when you guys are on it like this, i can't turn down that kinda service!
another question while i wait for my timer to finish.
initially i flashed pa. 2.11 then gapps along with doing cache business.
since then i flashed 2.12, but not gapps, and consequently having issues with play store (cant open)
can i just go to flashing 2.13 when it finishes downloading and then flash gapps after?
is the latest gapps jb-20120726-signed?
espionage724 said:
Wouldn't Kernel be more specifically tied to WiFi issues? I don't know what PA does to the kernel they include, but if your up to it, you could try another kernel, like franco.Kernel
Click to expand...
Click to collapse
a kernel is one of these things i have no clue about.
i had a mac many years ago, and that got a kernel error, so my knowledge is limited to that its something root related, or there abouts anyway xd
How does one go about implementing one of these kernel do-hickeys?
on a side note, my wireless icon used to show grey and blue.
blue meant connected, grey, i'm not sure.. sometimes worked sometimes didn't
ever since going to 2.12 i've had nothing but grey, seem to have connection as i am downloading from goo, but as mentioned in initial post, connection is definately worse than it was before hand.. any ideas?
`etcH said:
can i just go to flashing 2.13 when it finishes downloading and then flash gapps after?
is the latest gapps jb-20120726-signed?
Click to expand...
Click to collapse
Sorry I took a while, I was in class. First, you always have to reflash gapps when you flash an update or a new ROM.
When you change to a different ROM (i.e. from Slim Bean to Paranoid) it's recommended to do a full wipe/factory reset before flashing the new ROM.
So the procedure for new ROMs is this. Factory reset, wipe cache, wipe dalvik cache, flash ROM, flash gapps, reboot.
The procedure for a ROM update is the same, you just omit the factory reset.
The latest gapps is gapps jb-20120810. You can download it in Goo manager.
`etcH said:
a kernel is one of these things i have no clue about.
i had a mac many years ago, and that got a kernel error, so my knowledge is limited to that its something root related, or there abouts anyway xd
How does one go about implementing one of these kernel do-hickeys?
Click to expand...
Click to collapse
A kernel is what governs your CPU clock speeds and voltage levels, as well as some other things. To flash a kernel, you don't have to wipe anything, just flash the zip file. Whenever you flash a new ROM, it changes your kernel to whatever is stock for that ROM. So if you use a custom kernel, you will have to reflash it.
Sent from my Paranoid Nexus 7
p.a 2.13
might anyone have any idea why after;
wiping both cashes and installing p.a 2.13 then gapps
my youtube comes up with an error from the beginning, unable to start, same goes for if you click it in the app drawer.
i fiddled about with dpi size force and such, but to no avail.
some settings transferred but not all, like the ui, after switching ui back to what i wanted, tab small/mid
i started to recieve trebuchet has stopped working, this keeps popping up but you can just leave it in the back ground and work around it..
wish i could post this in the correct thread..
ah well.
thinking of just re-flashing them both, will do whatever i did this previous time, see if the error returns.
edit: just finished the reflashing of both, no trebuchet error as expected, the youtube one is back, same as the previous flash.
i really don't think i've done anything wrong, but i haven't seen anyone else reporting this error..
edit edit: simple uninstall and reinstall for youtube and problem solved.
hope its an issue localised to me.
`etcH said:
might anyone have any idea why after;
wiping both cashes and installing p.a 2.13 then gapps
my youtube comes up with an error from the beginning, unable to start, same goes for if you click it in the app drawer.
i fiddled about with dpi size force and such, but to no avail.
some settings transferred but not all, like the ui, after switching ui back to what i wanted, tab small/mid
i started to recieve trebuchet has stopped working, this keeps popping up but you can just leave it in the back ground and work around it..
wish i could post this in the correct thread..
ah well.
thinking of just re-flashing them both, will do whatever i did this previous time, see if the error returns.
Click to expand...
Click to collapse
Yeah I would reflash. It could also be a corrupted download, try re-downloading paranoid android 2.13 and then flashing the newer zip to see if that fixes it.
Sent from my Paranoid Nexus 7
Latest Downloads
CM10.1 http://d-h.st/i3V
CM10.2 https://drive.google.com/file/d/0B1V_hMyelDz0Rm1nenlqT2JKWkE/edit?usp=sharing AS OF 21.11.2013
UNOFFICIAL FAQ FOR CM10.1/10.2
DOWNLOAD AND INSTALLATION
Q: Where’s the download?A: The initial FXP release had an incorrect kernel – you can download a working version of ROM from here. http://d-h.st/TPT
This ROM has since been updated a download can be located here. http://d-h.st/i3V
If you wish to try a CM10.2 (that’s Jelly Bean 4.3 – have Sony actually released a 4.3 ROM yet?) one can be downloaded from the link above.You can also download the correct version of GAPPS for Jelly Bean 4.3 here. http://brintaylor.info/Android/CM/gapps/
For the CM10.2 build you should use this link to report bugs. https://docs.google.com/forms/d/185s...9UINQ/viewform
Uberlaggydarwin plans to take a 'light touch' approach to support via XDA, so don't necessarily expect an answer to a query if you post in this thread
It seems like FXP have delayed releasing for our device for now, but information about CM builds that are being actively supported and developed can be found in this thread for now.
Q: How do I install?
A: You need an unlocked bootloader and an installed recovery. BACK UP your current ROM to your external SD card. Put the ROM and GAPPS on your external SD card. Boot into your recovery, do the necessary wipes, flash the ROM, flash GAPPS, reboot, victory. Disclaimer: if it breaks your phone, it’s your fault.
Q: Do I need to install the supplied kernel before installing the ROM?
A: No, unlike older xperia models CWM is able to flash both the kernel and the ROM at the same time. There is no need to use fastboot or flashtools to flash the kernel first, just a working recovery and an unlocked bootloader on your phone.
Q: Can I use another kernel instead?
A: No, for now only the supplied kernel will work.
Q: I’ve installed the ROM but can’t find the play store?
A: Immediately after installing the ROM you should install the 4.2.2 version of GAPPS (Google Apps) – this installs the play store and several other applications that Google regard as essential to the Android experience. This can be found here – http://goo.im/gapps/gapps-jb-20130812-signed.zip
Q: How do I update to the latest version of the ROM?
A: Once you’ve downloaded the latest version to your SD card, boot into recovery. No need to wipe your data, though you probably should wipe cache and dalvik cache (I don’t know whether this is done automatically as part of the installation but it can’t do any harm). You don’t need to install GAPPS again as this is a firmware update, not a new installation.
However if you’re moving between versions i.e. 10.1 to 10.2 you should definitely do a factory reset – the ROM may well work fine without a data wipe, but it may not and any problems might not be immediately noticeable (making bug tracking difficult). I would advise you NOT to report bugs if you’ve moved between android versions without a factory reset.
Q: When will they release a version that works on a locked bootloader?
A: Never. Some the features of the ROM simply won’t work very well/at all on a stock kernel. If you are rooted you can simulate some of the features with apps and mods though.
POST-INSTALLATION QUESTIONS
Q: I’ve installed the ROM – I can use Titanium Backup to reinstall all my apps right?
A: Yes and no. They may work fine, they might not – you are better off letting Google’s back up service restore all your apps. If you restore an app using Titanium or similar software and it’s buggy, there’s no point reporting it – re-install the app instead, perhaps even the ROM.
Q: 4G isn’t working – what do I do?
A: It’s not enabled by default on CM10.1 so you must do the following.
Go to the dialpad/phone.
Dial in the this number: *#*#4636#*#* (This will bring up "Phone info").
Tap WCDMA from under "Set preferred network type".
Select "LTE/GSM/CDMA auto (PRL)".
The 4G LTE network should now be activated.
Q:Where’s USB mass storage?
A: After ICS Google stopped including it in their Android builds, as such mass storage mode is not a feature that was kept by CM for Jelly Bean. Individual manufacturers do what they want though, which is why Sony, Samsung and others still have it. Skilled modders may be able to add to ROMS based on this development, I reckon they might be able to patch this one to include it too
Q: This ROM is buggy as hell and drains my battery – how do I let the developers know?
A: Logcat and/or a kernel log - or it didn’t happen for bugs.
Better battery stats for battery drain.
There are lots of guides out there showing you how to take logs and how to record battery stats.
Anecdote – I activated Google+ yesterday as I like the auto-photo upload feature but wakelock detector revealed it was killing my battery (I think it’s dodgy on stock too). The choice was the app or the ROM, I chose the ROM.
Q: After installation something random doesn’t work – what do I do?
A: Check the thread to see if other users have mentioned the issue and to see if the developer has posted a solution. Also, you’re on XDA, you’re an advanced user, you have unlocked your bootloader, thrown out your warranty and accepted the consequences. So please try to resolve the issue yourself. In general if you are having a problem and no one else is, it will be a problem with your phone/download/installation.
Phone - obviously a hardware fault can't be foreseen by the developer and have you unlocked your bootloader!
Download - Most downloads are fine. But I've flashed enough ROMS to know that sometimes a file gets corrupted and sometimes they say they are complete when they are not. Sometimes I've been careless and clicked on the wrong download, sometimes the website hosting the site is haveing a a bad day, sometimes the developer puts the download in the wrong place too The first things to check are the name and size of the file - if these tally you're probably fine to install. If you want to be extra cautious you can check the MD5 hash to see if your download matches. Sometimes the file gets corrupted on upload - nothing anyone can do about that...
Installation - (Please back up your orignal ROM). Typically you'll be installing this ROM using a recovery from another ROM/kernel/MOD - so if you have problems installing , it might be that you have a bad recovery.
The wipes really need to be done to ensure the smooth running of your phone, but as you've backed up, the 15 seconds you spend properly wiping should not be much of a chore.
If you're one of the first downloaders, I guess there is some merit in saying you couldn't install, but if it's been out for a while and there are loads of posts saying 'what a great ROM' there's little point posting 'won't install'. Describe exactly what you've done and someone might help.
Bear in mind there are apps/hardware that the developers of this ROM won’t have heard of/care about - so if something doesn’t work properly on your phone it could be for numerous reasons. Either way, this may be something you have to live with. Alternatively, if the app is essential to you, you’ll have to return to a backup.
Remember this ROM is in development, there are no promises of perfection and no one is forcing you to use it. However, the right kind of feedback is always welcomed by the developers and may be acted on – the wrong kind will often be ignored.
Q: What does a perfect bug report look like?
A: Go here. http://forum.xda-developers.com/showpost.php?p=46935640&postcount=313
Q: What are the known bugs?
A: FM radio doesn’t work.
A: Attempts to offline charge cause the phone to boot.
A: 4G activation is not remembered between boots for CM10.1.
A: For 10.2 there is a known battery drain issue related to WiFi. See the solution here. http://forum.xda-developers.com/showpost.php?p=46923723&postcount=301
The following issues have been reported by some users, but others say it doesn’t affect them. They are regarded as hardware issues – anecdotal ‘me too’ posts will be ignored. However, supply a log and your phone’s date of manufacture and the developer may look into it (this might help you prove that your phone is faulty, so it’s a worthwhile exercise).
Erratic touch screen response.
Reading external SD Card in recovery and in use.
As others have said this is possibly the most stable first CM build they’ve encountered and I agree – it’s definitely suitable for daily use. I've been using it from release and haven't had a single reboot/app crash or freeze.
http://uploaded.net/f/q3au96
CM 10.1 released for huashan
Its cm for our phone right?!??
Sent from my ZTE Blade G using xda app-developers app
Thanks for sharing. I saw yesterday in the changelog that both 10.1 and 10.2 where announced on FXP 242 (10.1 in beta and 10.2 in alpha), but I can't find the 10.2 download anywhere.
Maybe they don't publish public download links for alpha versions ?
Parkside said:
...no announcements, I can't keep it to myself. You'd do the same right?
Click to expand...
Click to collapse
Its safe to download huanshan cm file for our phone.(know that huanshan is code name for our phone)????
Sent from my ZTE Blade G using xda app-developers app
Yes take a look
karma123 said:
Yes take a look
Click to expand...
Click to collapse
Wooohooooo im so happy i cant wait to test itThanks to FXP team !
When i flash it im gonna make review wohoooooo
Sent from my ZTE Blade G using xda app-developers app
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
karma123 said:
Yes take a look
Click to expand...
Click to collapse
Can you tell me what file to download??
Sent from my ZTE Blade G using xda app-developers app
Download this :- http://uploaded.net/file/7ntq0zp6/from/q3au96
Flashed and booted. Its nice. But some screen flickering while scrolling. Like in settings etc etc. But that can resolve with enable the " Disable Hardware Overlay" option from Developer Settings
What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks
Are mirrors allowed? Can somebody mirror this file? Im sorry but uploaded has failed me several times already...
mmm273 said:
What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks
Click to expand...
Click to collapse
Now only i flashed this. I dont have any apps installed. So performance is awsom now. Free RAM is 509 and used 333
ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...
Screen Flicker
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks
I have the flickering too ! And the phone often soft freezes. Seems like the app isnt updated anymore on screen. It can also be just the keyboard for example. Hiting recent tasks unfreezes it but systemui sometimes freezes until reboot.
Sent from my C5303 using xda app-developers app
uberlaggydarwin said:
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks
Click to expand...
Click to collapse
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...
mmm273 said:
ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...
Click to expand...
Click to collapse
I'd like to see a screen of that score. Seems a bit too high. Sure you have the SP ?
You're using V4 ofcourse, my bad.
Bootloader
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Hey, Make a backup, you need an unlocked bootloader for this. Then wipe all cache and data etc. then flash the rom on your phone
jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Well asfaik CM requires a custom kernel which can only be installed on a phone with unlocked bootloader. Hope ive helped.
Rajeev said:
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...
Click to expand...
Click to collapse
LOG"S OR IT DIDN"T HAPPEN . I'm serious.
I'm downloading this release to test but I can't help much if you don't provide logs.
Are you sure its not auto-brightness being turned on as auto-brightness doesn't work very well in stock so the changes are probably more noticeable.
Reboots work perfectly fine for me..
On the recent test builds I haven't had a reboot issue but as you know the kernel is temporary so I'll redo it when 4.3 comes out....
WE NEED LOGS.
Introduction
Though CyanogenMod always claimed to be open-source, there were only few versions that had an open userspace (Some drivers and firmware have always been proprietary, but it's not CMs fault).
The first CM version I ever installed on a device was CM7 and it contains koush's proprietary ROM Manager app. CyanogenMod 9 seemed to have no proprietary parts, but since CM10 they included Google Analytics Client library (libGoogleAnalyticsV2.jar) within cmstats in the settings app (so it's not even possible to disable it). In CyanogenMod 10.1 CMAccount was included. It relies heavily on Google's Cloud Messaging service and includes the proprietary Google Play Services Client library (google-play-services.jar).
There are some people here at xda (including myself) that installed CyanogenMod because it does not ship GAPPS and is a fully (except vendor files) open-source and free rom. Since i noticed it's not, i started building CM without these closed-source stuff, but it's a pity to do so. That's when the idea of freecyngn started.
What is freecyngn
freecyngn is a tool you can run from recovery, that removes some known proprietary things (or apps relying on proprietary extensions) from CyanogenMod. At the moment this is Google Analytics (from CMStats in CM10/11), CMAccount, LockClock, SetupWizard, Voice+, VoiceDialer and WhisperPush.
Installation Instructions
Copy or download the zip file to the sdcard of your android device
Boot your device into recovery.
If not already done, install CyanogenMod as usual from recovery - DO NOT REBOOT
Install freecyngn as if it was a rom, but DO NOT WIPE /system before
CyanogenMod 12/12.1The version for CyanogenMod 12 should not be used on nightlies before July 9, 2015!
Changelog
v1.0: First release for CM12
Downloads
Latest release (v1.0): https://github.com/mar-v-in/freecyngn/releases/download/v1.0/freecyngn-flashable-cm12.zip
All releases: https://github.com/mar-v-in/freecyngn/releases
Source: https://github.com/mar-v-in/freecyngn
CyanogenMod 10/11
Changelog
v0.5: Latest fixes, better logs
v0.4.1: Remove LockClock (uses Google Play Services)
v0.4: Adapt to latest changes, remove VoiceDialer as well
v0.3.1: addon.d based auto repatching
v0.3: fixed logging
v0.2: Now creating logfile: /system/freecyngn/log
Downloads
Latest release (v0.5): https://github.com/mar-v-in/freecyngn/releases/download/v0.5/freecyngn-flashable-cm1011.zip
All releases: https://github.com/mar-v-in/freecyngn/releases
Source: https://github.com/mar-v-in/freecyngn
How it works (technical stuff)
freecyngn disassembles (using [bak]smali) the CyanogenMod settings app and removes the proprietary Google Analytics component. It then replaces it with NoAnalytics, so that existing bindings from cmstats do not break and reassembles the settings app.
FAQ
Q: My recovery hangs while flashing?
Q: Why is this script so slow?
A: freecyngn need plenty of time and is sometimes even slower than flashing the rom itself. This is bcause most recoverys underclock the cpu, which is no problem for just copying files from zip to partition or format a partition, but it is a problem for disassembling and reassembling, which are cpu intensive tasks.
Q: Do I need to apply the patch after every update?
A: Since v0.3.1 this is no longer needed. Patching is done automatically.
Q: What's about other custom ROMs?
A: AOKP is patchable with freecyngn as well. Paranoid contains Google Analytics in the proprietary ParanoidSettings app instead of the system settings and thus does not work with this patch. OmniROM does not contain Google Analytics. Note that some slimmed-down CM/AOKP-custom-builds will not work with freecyngn. If you use such, check the log file /system/freecyngn/log after flashing.
XDA:DevDB Information
freecyngn, Tool/Utility for the Android General
Contributors
MaR-V-iN
Source Code: https://github.com/mar-v-in/freecyngn
Version Information
Status: Stable
Current Stable Version: v1.0
Stable Release Date: 2014-08-07
Created 2013-12-01
Last Updated 2016-07-02
Its work in android 4.4 kitkat Ah?
Pretty interesting stuff, I didn't knew you could assemble/disassemble dex files on the device. Anyways, I wanted to tell you, you can just boot the cpu freq to make it faster.
just grep cpuinfo_max_freq and use that number for scaling_max_freq
This is really cool... definitely going to try this out,
Subscribed
Flashed on cm10.2 on evo3d. Only took about 3seconds for me. Thanks
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
MaR-V-iN said:
Introduction
What is freecyngn
freecyngn is a tool you can run from recovery, that removes some known proprietary things (or apps relying on proprietary extensions) from CyanogenMod. At the moment this is Google Analytics (from CMStats), CMAccount and Voice+.
Click to expand...
Click to collapse
I always remove CMAccount and Voice+ as they are system apps but isn't removing CMStats the same as disabling About Phone>CyanogenMod Statistics>Enable Reporting?
ela1103 said:
Its work in android 4.4 kitkat Ah?
Click to expand...
Click to collapse
I'm on beanstalk 4.4 and worked fine.
Sent from my GT-N7105 using Tapatalk 4
Thanks, will try this now!
jdstrydom
thank for u reply
Sir what is the use of it
I.mean by removing the google support what will we get
And how is this useful
Please tell me sir
ela1103 said:
Its work in android 4.4 kitkat Ah?
Click to expand...
Click to collapse
I tried it on the CM11 build for mako, so I highly assume it's working on all CM11 based roms.
broodplank1337 said:
just grep cpuinfo_max_freq and use that number for scaling_max_freq
Click to expand...
Click to collapse
I'm aware of this method, but I don't think it's a good idea in general, because on some overclocked kernels cpuinfo_max_freq could be really unstable.
jbonetwo said:
I always remove CMAccount and Voice+ as they are system apps but isn't removing CMStats the same as disabling About Phone>CyanogenMod Statistics>Enable Reporting?
Click to expand...
Click to collapse
It's not removing CMStats completely but only the Google Analytics part. Sending stats to stats.cyanogenmod.org will still work.
Moreover, you can't really say if Google Analytics is disabled. Due to it being proprietary code, it could do nearly anything and the class initializer code is called, even if CMStats is disabled. (I assume they're not doing this, but you can;t know and they always could add this in a future version)
aditya rathee said:
I.mean by removing the google support what will we get
And how is this useful
Click to expand...
Click to collapse
First: This does not remove Google Support in general. You could still install GAPPS afterwards, but it would be kind of senseless.
Second: Some people think, that Google is not this "don't be evil" company they're proposing to be. And some people like the idea of privacy and not getting totally tracked by Google, so they do not install GAPPS. If this is not the case for you, then this is just not targeting you. I'm not going to try to convince anyone that privacy is a good thing
MaR-V-iN said:
I tried it on the CM11 build for mako, so I highly assume it's working on all CM11 based roms.
I'm aware of this method, but I don't think it's a good idea in general, because on some overclocked kernels cpuinfo_max_freq could be really unstable.
It's not removing CMStats completely but only the Google Analytics part. Sending stats to stats.cyanogenmod.org will still work.
Moreover, you can't really say if Google Analytics is disabled. Due to it being proprietary code, it could do nearly anything and the class initializer code is called, even if CMStats is disabled. (I assume they're not doing this, but you can;t know and they always could add this in a future version)
First: This does not remove Google Support in general. You could still install GAPPS afterwards, but it would be kind of senseless.
Second: Some people think, that Google is not this "don't be evil" company they're proposing to be. And some people like the idea of privacy and not getting totally tracked by Google, so they do not install GAPPS. If this is not the case for you, then this is just not targeting you. I'm not going to try to convince anyone that privacy is a good thing
Click to expand...
Click to collapse
ok ok
now i am gonna flash it
MaR-V-iN said:
It's not removing CMStats completely but only the Google Analytics part. Sending stats to stats.cyanogenmod.org will still work.
Moreover, you can't really say if Google Analytics is disabled. Due to it being proprietary code, it could do nearly anything and the class initializer code is called, even if CMStats is disabled. (I assume they're not doing this, but you can;t know and they always could add this in a future version)
Click to expand...
Click to collapse
Thank you for the info. I would not have thought to look at the Settings app for undesirable activities.
Found the following activities for Settings in Sys Tuner:
UsageStats
Settings$AnonymousStatsActivity
DeviceInfo$StatsReportReceiver
cmstats.ReportingService
Will be flashing your zip for a 'cleaner' solution than sys tuner in the near future.
And yes google is evil . Their handling of adblock and similar apps shows they're motivated by money and I wouldn't give a corp like that free reign over my device. But that's just me...
Ran this script on my rooted stock KitKat ROM @ Nexus 4 & 7, so far no abnormal activity observed on my devices...
So if we run this app, can we still use gapps or is that considered one of the tracking apps that will be removed?
flashed it on my 4xHD, will see how it will behave
i had really quick install of the zip file, like i would install kernel
that is normal or ?
because in op you say that install will take some time
Do you know if this will work on all cm based roms or only actual cyanogen?
Sent from my SCH-I545 using XDA Premium 4 mobile app
pr0di9y said:
Ran this script on my rooted stock KitKat ROM @ Nexus 4 & 7, so far no abnormal activity observed on my devices...
Click to expand...
Click to collapse
rrrrrrredbelly said:
Do you know if this will work on all cm based roms or only actual cyanogen?
Click to expand...
Click to collapse
This is only for CM-based roms that contain CMStats. The Script does nothing useful on Nexus stock or not-CM-based ROMs, these do not include Google Analytics in the Settings app (yes that's right: CM+GAPPS does more Google tracking than Google's stock)
The new v0.2 release creates a log file in /system/freecyngn so you can make sure everything worked great.
MaR-V-iN said:
This is only for CM-based roms that contain CMStats. The Script does nothing useful on Nexus stock or not-CM-based ROMs, these do not include Google Analytics in the Settings app (yes that's right: CM+GAPPS does more Google tracking than Google's stock)
The new v0.2 release creates a log file in /system/freecyngn so you can make sure everything worked great.
Click to expand...
Click to collapse
Does this explain why they have these stats on hand?
developer.android.com/about/dashboards/index.html
Disclaimer
I'm not responsible for anything that may happen to your device. I've tested this mod to the best of my abilities, but I can't guarantee anything. Make a complete backup before applying any of these changes. If you brick your device, boot loop, lose data, or etc...again, I'm not responsible.
CM12 - Working
- CM12S YNG1TAS0YL with stock kernel
- CM12 nightly with stock kernel
CM11 - Working
- CM11S XNPH30O, XNPH33R, XNPH38R, XNPH44S, and XNPH05Q with stock kernel
- CM11, PAC-man, crDroid with most recent kernels
- franco r35 kernel
CM12.1 - Not Working
- CM12.1 nightly (bootloop)
CM11 - Not Working
- LiquidSmooth ROM (mediaserver seg faults immediately)
- OmniROM
Also, I found a commit in the CM source that adds Voice Wakeup options to the Settings app. If the ROM doesn't have this code compiled into their Settings, the mod will probably not work. You'll still be able to go through the training process, however, I don't believe Google Now will launch because the intent action is never being set.
Instructions
1.) Backup any important data on your phone (files, pictures, etc.)
2.) Boot into recovery. I use and have only tested with TWRP
3.) Make a nandroid backup
4.) Flash the mod
5.) Reboot
Recovery
If you encounter any issues (e.g. bootloop) or just want to remove the mod, go into recovery and restore just the System partition from the backup you made earlier (this will preserve your Data partition).
After Installation
After installing, you'll get a notification to enable Voice Wakeup and to train your voice. You can do this now or skip it. It can always be setup later by going to:
CM11: Settings --> Voice Wakeup --> Retrain your voice
CM12: Settings --> Language & Input --> Voice Wakeup --> Retrain your voice
Also...
1.) Go into the Google Now settings and disable "OK Google" detection settings.
2.) Disable your lockscreen if on CM11S or CM12S...other CM11/CM12 based ROMs should work fine since the apk is signed correctly. Some users have reported being able to use a 3rd party lockscreen (e.g AcDisplay) as a work around for CM11S.
If something is not working for you, I need the following or I can't help...
- The ROM you're using (date/version too)
- The kernel you're using (date/version too)
- A description of the problem
- A logcat of the problem in action
Changelog
Code:
[I]4-14-2015[/I]
- New test version for CM12 based ROMs. I believe this should work with most kernels.
[I]Version 2.0[/I]
- CM11 based ROMs only
- Updated mixer_paths.xml with more recent version from CM11
- Deodexed, signed, and zip aligned VoiceWakeup.apk. The app can now bypass the lockscreen on CM11 based ROMs
Disabling the lockscreen is still necessary for CM11S ROMs because those keys aren't public
- Added a "loud" version. It increases the microphone volume levels to make it more sensitive
[I]Version 1.0[/I]
- Initial Release
Woow. It seems working flawlessly
me wanty. Hopefully you can post a how to in the near future
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
jojo_whit3 said:
I bought the OnePlus One in August because I was interested in the always on listening feature that they showed off back in the Spring. So when I actually received the phone, I was pretty disappointed to learn that they took the feature out before shipping. Over the past couple weeks, I've been working on a way to get this feature back in the phone and I think I finally got it working pretty well. I've only tested it on the 25R and 33R builds, but it should work on most ROMs for this phone. The mod uses the always on low power core, so there's no significant drop in battery life. I know Qualcomm has some licenses for this IP, so I'm still trying to figure out if I can legally post the mod here. But in the meantime, here's a demo of it working...
Click to expand...
Click to collapse
Just curious, would this mod stop ota updates and if so is it easily reversible? Looks really nice.
Sent from my A0001 using Tapatalk
share it pls!
Overdose1986 said:
share it pls!
Click to expand...
Click to collapse
Did you read the OP?
I know Qualcomm has some licenses for this IP, so I'm still trying to figure out if I can legally post the mod here.
Click to expand...
Click to collapse
Transmitted via Bacon
looks cool, do keep us updated if you are able to share this "legally" or can you pm me the "not so legal" way? LOL
I didn't know I wanted this until now
That looks awesome
I've been trying to contact someone from the Cyanogen team to get some more information about posting this. If anyone has any contact info, either send me a PM or send them over to this thread.
To give a little more information about this mod, its essentially a port of the VoiceWakeup.apk I found here. If you use apktool to disassemble this file, it's easy to tell it came directly from Qualcomm. However, if the Cyanogen team intended to release this apk with the phone initially, then I'm assuming they already have some agreement in place with Qualcomm. So hopefully that also means it'll be ok for me to post this mod in the near future.
26.2man said:
Just curious, would this mod stop ota updates and if so is it easily reversible? Looks really nice.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
You would still be able to download the OTA updates, but you wouldn't be able to apply them since there would be changes to your file system. If you make a nandroid backup in recovery, then anything is easily reversible.
Thanks. Hope you can release this soon.
Sent from my A0001 using Tapatalk
Looks great, wonder if the cm team is working to make it work by choosing you own wake up command. Had it on my find 7a and saying snapdragon was strange
If it's already freely available then it's unlikely to cause any more issues, depends on what did you do to"port" it I guess.
All the cm11s apps have been made available, so if it came from an existing rom I can't really see much of an issue. But I'm not a lawyer
Alternative is to post a walkthrough of your changes to the original.
Sent from my A0001 using Tapatalk
Awesome work, hopefully you're and to post it up for us eventually.
Hi Everyone...I did a little thread cleaning. Please, lets not harass the OP about when this will be released. Like everything else on xda, it will be released when the developer is ready. Just as a reminder to everyone,
yes this is a hackers site, but certain things are not allowed. If the OP wants to make sure that he isn't violating CMs or Qualcomm's Intellectual Property then we should let him do this to his own satisfaction. Nobody
wants to see a modification removed because CM or Qualcomm complained.
Thanks!
This looks really good! Would love to have this feature, keep it up man
If you're worried about posting the modded APK and the IP issues, can you at least let us know what you modded so we can do it on our own?
had a quick play with it earlier,
Cm 11 nightly contains the background libs (except liblisten.so) but there's some java calls missing. Curious that cm have left most of the libs in place.